- Original Message -
From: Francois PIETTE francois.pie...@skynet.be
To: ICS support mailing twsocket@elists.org
Sent: Thursday, February 04, 2010 9:00 PM
Subject: Re: [twsocket] HttpCli TransferEncoding
Don't forget about proxies and firewalls. They probably has also to
support
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
How can I set the transfer encoding to chunked and send seperate chunks ?
thx,
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
How can I set the transfer encoding to chunked and send seperate chunks ?
From what I see there is no easy way to do it with the HttpCli, without
overriding some methods or/and add your own PostChunked
Paul wrote:
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
It is server's TransferEncoding, that's why it's read only.
How can I set the transfer encoding to chunked and send seperate
chunks ?
THttpCli supports chunked encoding when it receives
: Thursday, February 04, 2010 5:18 PM
Subject: Re: [twsocket] HttpCli TransferEncoding
Paul wrote:
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
It is server's TransferEncoding, that's why it's read only.
How can I set the transfer encoding to chunked
Component Suite (ICS)
http://www.overbyte.be
- Original Message -
From: Paul paul.blommae...@telenet.be
To: ICS support mailing twsocket@elists.org
Sent: Thursday, February 04, 2010 6:39 PM
Subject: Re: [twsocket] HttpCli TransferEncoding
So it's currently impossible with THttpCli
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
To: ICS support mailing twsocket@elists.org
Sent: Thursday, February 04, 2010 5:18 PM
Subject: Re: [twsocket] HttpCli TransferEncoding
Paul wrote:
I can't get the client working with it.
httpCli.TransferEncoding
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
I wonder what you want to achieve?
speed.
If you managed to keep
one conection alive by sending an infinite data stream
it won't ensure that the other connection, your work
connection, won't be disconnected nevertheless.
Paul wrote:
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
I wonder what you want to achieve?
speed.
If you managed to keep
one conection alive by sending an infinite data stream
it won't ensure that the other connection, your work
connection, won't be disconnected
If I got you right, you use ICS HTTP server and it disconnects
the connections, right? If you are on v7 I hope you noticed that
the HTTP server component got a new timeout feature that
disconnects clients even when they established
Keep-Alive connections? It's ON by default.
I use a modified
If you managed to keep one conection alive by sending an infinite data
stream
it won't ensure that the other connection, your work
connection, won't be disconnected nevertheless.
Should be possible if you write both server and client though.
Don't forget about proxies and firewalls. They
Don't forget about proxies and firewalls. They probably has also to
support it
It should be possible imho.
it's like sending a large file in pieces.
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Don't forget about proxies and firewalls. They probably has also to
support it
It should be possible imho.
it's like sending a large file in pieces.
Not exactly. Any device analysing the content has to decode chunks.
--
francois.pie...@overbyte.be
http://www.overbyte.be
--
To unsubscribe
Paul wrote:
With Http(s), you have to send a new request each time for each
message and there is a huge delay if multiple proxies are in between.
And you never know what those proxies do.
That makes me believe that HTTP isn't the right protocol for the job.
--
Arno Garrels
--
To unsubscribe
And you never know what those proxies do.
That makes me believe that HTTP isn't the right protocol for the job.
I wish I had another choise, but I'm not.
In the end, only https is allowed.
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Not exactly. Any device analysing the content has to decode chunks.
I still don't get it right then.
What is the problem with sending a large file and pause the transfer for a
few seconds in between ?
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
16 matches
Mail list logo
