Thanks all,
I've tested with POST and GET and I can use either.
Both server and client are special purpose applications.
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at
On Sep 23, 2006, at 08:32, Paul wrote:
Hi,
What is the best method when I send a stream to a server, but expect a
stream back from the server with the same request ?
It may sound silly, but think about the names of the methods to
understand their original intention:
GET - To request a
POST seems to be the only way to send long data to HTTP servers.
Regards,
SZ
- Original Message -
From: Paul [EMAIL PROTECTED]
To: twsocket@elists.org
Sent: Saturday, September 23, 2006 3:32 PM
Subject: [twsocket] Http Get or Post
: Hi,
:
: What is the best method when I send a
POST seems to be the only way to send long data to HTTP servers.
It's the most logical method for sending data, but I need to receive a
stream back with the same request.
If memory serves me well, the length of an URL can be 32k long with Http1.1,
so maybe I can still use the Get method.
I,m
@elists.org
Sent: Saturday, September 23, 2006 4:43 PM
Subject: Re: [twsocket] Http Get or Post
: POST seems to be the only way to send long data to HTTP servers.
:
: It's the most logical method for sending data, but I need to receive a
: stream back with the same request.
: If memory serves me well
Scrive Paul [EMAIL PROTECTED]:
POST seems to be the only way to send long data to HTTP servers.
It's the most logical method for sending data, but I need to receive a
stream back with the same request.
You will receive data if you use POST, if the server send it to you of
course :-)
If
