Re: persistent TCP connection over page reloads ?
- From: Thomas 'PointedEars' Lahn <PointedEars@xxxxxx>
- Date: Wed, 16 Apr 2008 10:58:56 +0200
mel wrote:
On Apr 15, 2:51 pm, Thomas 'PointedEars' Lahn <PointedE...@xxxxxx>
wrote:
mel wrote:
I need a persistent TCP connection with my web server over pageNo, you don't. Besides, persistent *HTTP* connections (which is what you
reloads.
mean) have to be supported by both client and server, and they won't help
you here. Whether the HTTP connection is persistent or not, the current
wait. aren't HTTP connections built on top of TCP ?
Yes, they are. But that does not matter.
global execution context of the script engine is destructed when another
resource is being navigated to.
window.name & globalStorage & userData aren't destructed
As for window.name, there is insufficient proof for that.
This means that, even if the user goes to a different page (inChances are that it is kept alive already, as persistent connections are the
my domain), I want to keep a TCP connection live.
HTTP/1.1 default. You don't seem to know what TCP is.
You don't seem to understand my question.
You don't seem to have asked the right one.
I know I can do something similar with globalStorage in FF,Or simply cookies, supported by all scriptable UAs through the same mechanism.
window.name & userData on IE,
cookies go back to the web server.
Cookies are stored client-side. They are submitted to the Web server only
on request.
i don't want them to. cookies only store strings, which doesn't work for
me either (unless I can serialize a xmlhttprequest).
but those storages only hold strings.What else would you want to store? Even an image can be represented by a
sequence of characters.
A XmlHttpRequest can't.
Yes, it can. Reading it back is the difficult thing.
I want to store a XMLHttpRequest object and not destruct it over page
reloads.
Tough luck. You will need a persistent container object for your persistent
execution context, say a frame or another window.
Actually, it doesn't have to be a XMLHttpRequest, that is why I didn't
mentioned HTTP.
I beg your pardon?
As far as the connection is alive over page reloads, it works for me.
That depends on what you call a "page".
It could be a ftp session, or any other kind of connection through js,
java applets, flash or whatever other technology you want to use (as
Stevo pointed out).
ISTM you don't want to use browser scripting.
And, AFAIK, I can't serialize a TCP connection (could be throughBut you can serialize objects.
XmlHttpRequest, etc).
I wonder if anyone knows if this is possible at all.That depends on what you are *really* up to.
maybe you didn't understand what I need.
Maybe you have not explained it properly.
[...]
I want to stream data from the server to the client (I guess this is
called push, reversed ajax, or watever), but once the streaming starts
my server can't loose the connection with the client (the browser).
any ideas ?
You have explained what you want but not why. ISTM you are on the wrong
track, and in the wrong newsgroup anyway.
Please trim your quotes.
PointedEars
--
Use any version of Microsoft Frontpage to create your site.
(This won't prevent people from viewing your source, but no one
will want to steal it.)
-- from <http://www.vortex-webdesign.com/help/hidesource.htm>
.
- Follow-Ups:
- References:
- persistent TCP connection over page reloads ?
- From: mel
- Re: persistent TCP connection over page reloads ?
- From: Thomas 'PointedEars' Lahn
- Re: persistent TCP connection over page reloads ?
- From: mel
- persistent TCP connection over page reloads ?
- Prev by Date: Re: <div> blocks in same position?
- Next by Date: Re: anonymous functions; naming of and firebug
- Previous by thread: Re: persistent TCP connection over page reloads ?
- Next by thread: Re: persistent TCP connection over page reloads ?
- Index(es):
Relevant Pages
|