-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 16, 2007, at 2:27 PM, Andrey wrote:
Hi
I have a xmlrpc service running in web2, application high lvl
structure.
I wonder what should i do if i want to know when the client's
connection is
finished,
so that i can flush some transaction.
HTTP is a stateless protocol. The TCP connection is completely
unrelated to the Request & Responses. As a result web2 exposes no
way of dealing with the underlying connections. There are lots of
ways to shoehorn state into HTTP (sessions via cookies (or if you're
using XML-RPC just an argument that is passed to all the commands.))
99.9% of the time the underlying TCP connection is meaningless.
- -David
http://dreid.org/
"Usually the protocol is this: I appoint someone for a task,
which they are not qualified to do. Then, they have to fight
a bear if they don't want to do it." -- Glyph Lefkowitz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGS+bMrsrO6aeULcgRAqbnAJ49AVe3+HAGHX+1VYxkTygKreictwCghffQ
XCcEQJMng3AM5ZNNDaq/5kQ=
=ZkhU
-----END PGP SIGNATURE-----
_______________________________________________
Twisted-web mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
