On May 16, 2008, at 02:50, Tobias Rapp wrote:
> DZ-Jay wrote:
>> A way to create a multi-part response is to encapsulate
>> it as a MIME 822 message. Here's some basic information on this:
> I stumbled over the following lines on that page:
> | The situation is even worse if you need authentication for each image
> | preview - you must do tenth of authentication requests against user
> | database, separated for each http request.
> Is that really true? I thought that in the meanwhile it is common
> behavior to establish and keep one TCP connection for all HTTP requests
> until the page is loaded. And that the authentication is remembered for
> a established TCP connection.
Yes, it's true: each resource is retrieve individually by an HTTP
request, and each needs to contain the authentication credentials.
Typically, you authenticate only on the first request and generate an
authentication token, which is reused by the client on each subsequent
request. Then all you need to do is validate the token instead of
doing the full (and probably expensive) authentication.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be