On Thu, 2008-06-19 at 12:13 -0700, David Gallardo wrote:
I've read section 9.1 and don't see how this would be in violation of the
spec. I intend to use the body merely to specify the query, the server
doesn't preserve it, so it's an entirely safe, idempotent retrieval
operation--like any
Well, from what you quote from 91.1., it looks like, at worst, I would be
doing something I SHOULD NOT which means it's not a violation of the spec.
RFC 2119 says things with this label may be acceptable or usefule, but
implications should be understood and the case carefully weighed.
The bit
Quintin Beukes wrote:
I'm not sure why accessing it from different threads would cause this
to happen? Could you explain this please.
Quintin
I am only guessing here. All I am saying HTTP connection objects are not
threading safe. The only method one can safely can from a different
thread
So how else to do a retrieval?
olegk wrote:
David Gallardo wrote:
Well, from what you quote from 91.1., it looks like, at worst, I would be
doing something I SHOULD NOT which means it's not a violation of the
spec.
RFC 2119 says things with this label may be acceptable or usefule, but
Yes, I'm asking the latter question, how to do a retrieval based on a
largish-entity--while trying to adhere to the semantics, idempotency,
intention, etc. of HTTP.
@D
Sam Berlin wrote:
So how else to do a retrieval?
If you are asking how to do this in code -- I mentioned earlier on
