I need a client function that connects to server,
send data and close connection.
You'd better design your application using the asynchronous mode which is
the native mode for ICS. In short, use the events !
Here, the result is false everytimes because the socket is never
connected.
This is
Hello,
Could you look at the new code below:
procedure TWebConnection.ConnectionDataSentISAPI(Sender : TObject;
Error : WORD);
begin
sendError := Error;
sendComplete := true;
end;
function TWebConnection.SendSync(Data: String): boolean;
begin
Result :=
Also, function TWebConnection.SendSync(Data: String): boolean;
is never called from the modified DXISAPI. It is just for I believe
the HEAD command. (I know Length(Data) can return wrong info.)
Best Regards,
SZ
On 11/22/06, Fastream Technologies [EMAIL PROTECTED] wrote:
Hello,
Could you
What does Does not work means ? Any error, exception, symptom ?
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Fastream Technologies [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, November 22, 2006 9:24 AM
Subject: Re: [twsocket]
As I wrote before, the downloaded picture (from the php5ISAPI.dll) is
corrupt! Most of the picture is grey.
On 11/22/06, Francois Piette [EMAIL PROTECTED] wrote:
What does Does not work means ? Any error, exception, symptom ?
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original
Francois PIETTE wrote:
Using hgWillSendMySelf I noticed the proxy server immediately connects
the client to the server and the connection is kept open as long as I'm
sending data. If the proxy server does the same for the long HTTP post
it would provide a very valuable tool for what I need.
Alright, found the bug myself and fixed now. It is the result :=
sendError 0; line. It should have been the opposite way...
THANKS!
SZ
On 11/22/06, Fastream Technologies [EMAIL PROTECTED] wrote:
As I wrote before, the downloaded picture (from the php5ISAPI.dll) is
corrupt! Most of the
This is a new, free component for ICS V6, that dramatically simplifies
the use of TWSocket and TWSocketServer, avoiding needing to understand
many internals of ICS, in the same way as the FTP and HTTP components do
for those protocols.
I've found that many of my applications that need to
I'll re-explain how my downstream (that is - HTTP
download) connection works. The client requests a document from my web
server. It does this going through the proxy. The server response (200
OK), does NOT send an Content-length header and starts sending the
document very very slowly, but it
Francois Piette wrote:
This is proxy implementation dependent. The proxy could buffer the document
up to some point and then give up and forward everything. It could also
handle document differently according to the content-type.
If you consider this would not happend, then it's OK for me.
Do you see any wholes in my logic?
I don't.
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be
- Original Message -
Do you see any wholes in my logic?
I don't.
Partials?
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If the reader of this message is not the intended recipient,
you are hereby notified
Right now, though, it's working TOO good g
My ClientDataAvailable() procedure (assigned to my TWSocketServer's
OnDataAvailable() event as shown below) is firing twice--for every message I
send my app from my test utility, ClientDataAvailable() gets fired twice!
procedure
I notice in the Debug Window (BDS 2006) that the following are called, one
right after the other:
WSocket.TCustomLineWSocket.TriggerDataAvailable(0)
WSocket.TCustomSocksWSocket.TriggerDataAvailable(0)
WSocket.TCustomWSocket.TriggerDataAvailable(0)
Is this why my ClientDataAvailable() is called
My bad!
I fixed it by moving the line to process the msg outside of the strip out
the carriage return and line feed loop:
Was:
procedure TfClientMain.ClientDataAvailable(Sender: TObject; Error: Word);
var
iMsgCode, iMsgTableID: Integer;
begin
with Sender as TTcpSrvClient do begin
{ Since
BTW, what is the netiquette regarding mailing lists as to snipping
previous
parts of the thread--should I cut out everything below this, or leave it
be
(leaving it be until I hear/read otherwise).
You should keep just enough for everybody to understand what you are talking
about.
--
16 matches
Mail list logo
