On 7/13/07, Robert Cummings <robert@interjinn.com> wrote:
This isn't possible since you can't request a connection to the client's
machine. Only the other way around.
hmm... in that case perhaps the open connection could be employed and
the feature used selectively; only on certain pages for instance ?
im thinking mainly of a monitoring page; like an app that shows a servers
state,
or stock quotes or something.
the main reason i dont like a javascript timer refreshing the page is
sometimes you
dont want the whole page refreshed; especially when halfway through filling
out a
form on the page ;)
-nathan
On 7/13/07, Robert Cummings <robert@interjinn.com> wrote:
On Fri, 2007-07-13 at 14:59 -0400, Nathan Nobbe wrote:
On 7/13/07, Robert Cummings <robert@interjinn.com> wrote:
I haven't looked at the code for Xaja and in no way do I want to
subtract from its potential, but I'm going to guess that in some way
it
holds the HTTP connection open and as such is an expensive feature.
Also, I'm not entirely sure, but isn't that the principle that
Comet
uses?
As i said ive only imagined such a feature. In my imagination i
wonder if it is possible to
track the clients address in a data structure within the application.
Then a connection could be
established whenever a push was needed.
This isn't possible since you can't request a connection to the client's
machine. Only the other way around.
I also think the app would have to track the last page
a user requested in order to realize such an implementation. This
*should* be feasible using
sessions because whenever the client makes a new request the last page
variable could be updated.
I havent seen nor heard of Comet; would you mind providing a link?
http://ajaxian.com/archives/comet-a-new-approach-to-ajax-applications
Cheers,
Rob.
--
...........................................................
SwarmBuy.com - http://www.swarmbuy.com
Leveraging the buying power of the masses!
...........................................................