Hello,
Socrates ? is this a freeware tool ? if it is, i'd like to try it. BTW when
you said 1000 req/sec, did you know how many connections that was opened and
closed/sec? does it uses persistent connection etc ? is this using a single
url or a replayed log file ? could you provide more info ?
BT
Hello,
Socrates is free but no longer available somewhere except
http://www.fastream.com/ics. I think it can support keep-alive as well. It
is pure Win32/Delphi program.
Unfortunately I do not have a BSD here to try the web-polygraph... :(
Best Regards,
SZ
- Original Message -
From:
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 ?
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.o
POST seems to be the only way to send long data to HTTP servers.
Regards,
SZ
- Original Message -
From: "Paul" <[EMAIL PROTECTED]>
To:
Sent: Saturday, September 23, 2006 3:32 PM
Subject: [twsocket] Http Get or Post
: Hi,
:
: What is the best method when I send a stream to a server,
> 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 n
Hi Paul,
POST also pumps back a stream! Average URL length is 45 bytes and most
servers do not accept more than 1024 bytes. You should not trust GET for
posting data upstream.
Best Regards,
SZ
- Original Message -
From: "Paul" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Satu
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 :-
samuel wrote:
> Is there anything else that i miss, that should be noted for high
> performance socket apps ? Please share your experience and thoughts..
At first you should move to V6. In V6 any TWSocket instances in
a thread use the same, single window. If you run TWSocketServer
it may also help
