I have a question but Im not sure of the best way to word it atm. So Ill only try and write it down if anyone here might have a clue !!

/cryptic

Have used a bit of AJAX before, linked in with php script

not sure this is exactly what you mean

Yeah thats the ticket.

Do you know if the XMLHTTPRequest objects ever timeout/close the connection themselves ? I am hoping that the only timeouts/closures are driven by the server and not the client.

I know I should just knock up a prototype but tbh I am hoping that someone will know the answer


news just in:

http://ajaxpatterns.org/Timeout

I got an email from a friend that suggests that the client will never terminate the connection *YAY*

tis a very powerful tool, though it seems it is also a very vulnerable target as well

As vulnerable as any web service really, its down to design and implementation of each application

I guess it is as good as any other detergent

lmao @ Bear!

Quote from: bearI guess it is as good as any other detergent (Image removed from quote.)

(Image removed from quote.)

You tool

You have no idea how many shopping sites I have visted today for that one reason

lol!!!

planning to use ajax more on my second build of the company site at work.

using asp.net though, tis all i know  

Sam has been doing some next level sh*t on his software with Ajax. Website searches that auto update and refresh the results without changing browser pages and the like  :shock: Groovy stuff, it seems very powerful.

Think I may try out some AJAX stuff on my next project at work

Real-time (Insert bank product) performance dashboard..... OoOooOOOo  :mrgreen:

Just completed my first real-time reporting suite and everyone seems to love it.  Need to go to the next level as well.

"Wow, is this real-time as well?"

"Err, yeah, it sure is."

"You are a star."

"Thanks"

lol @ the real-time tagging there.

"real-time horsesh*t monitoring system!"

"Wow... were a company that deals with aircraft parts... WE WANT THAT!"

Say anything is "real-time" and management of any company seem to love it.

Its the RT stuff that I am looking into atm. It looks like whilst it can be done using the AJAX approach, it might not be the best approach; after all HTTP is not designed for continous data streams.

I plan on sticking together a proof over the weekend but I have a feeling that for the amount of data and concurrent browser connections I will need to scale to, a more standard message-queue/data-publishing model will be needed.