Re[6]: [twsocket] Receive result of the first ReceiveStr()calltwice-not resolved

2005-06-02 Thread Jack
Hello Sean and Francois, Thanks for testing it. You two are right. The second OnDataAvailable does not contain the http header. My bad! I'm still curious though, why the exception (It doesn't give me an exception on Delphi 2005!) causes the data to be received twice. -- Best regards, Jack Thur

Re: [twsocket] Upload file using http protocol

2005-06-02 Thread Francois PIETTE
You have to format your posted data according to the MIME standard. This has been discussed several times before. I suggest you scan the mailing list archives to find what has been said on the subject. There is a searchable archive here: http://marc.theaimsgroup.com/?l=twsocket You can download

Re[2]: [twsocket] Non-LineMode Protocol Sending and Receiving

2005-06-02 Thread Wilfried Mestdagh
Hello Wes, In addition to the advice of Francois is what I often do if designing a protocol that is both ascii data (for commands) and binary data packets, is to preceide the packet with a length in hexadecimal form (byte, word or dword). Wy ? Because if most of the data is ascii command then it m

Re: Re[4]: [twsocket] Receive result of the first ReceiveStr()calltwice-not resolved

2005-06-02 Thread Francois PIETTE
Your sample has the same broken logic that the first sample you sent to me had ! You haven't properly read or understood what I told you before. If you had correctly parsed the reply, you would immediately have found your problem. Anyway, Replace your OnDataAvailable event handler by this one:

[twsocket] Upload file using http protocol

2005-06-02 Thread robertovalente
How to upload a file if i have a client application in local computer and a WINCGI application on a Web Site ? (Cliente side and Server side) Thanks Roberto -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Vi

Re: Re[4]: [twsocket] Receive result of the first ReceiveStr()calltwice-not resolved

2005-06-02 Thread Sean Capstick
That's because the call to StrToInt generates an exception (at least on my system). As Francois mentioned earlier, you are assuming in the DataAvailable that you have the entire response, which you don't. On my system the event is triggered 4 times with various portions of the message. The

Re[4]: [twsocket] Receive result of the first ReceiveStr() calltwice-not resolved

2005-06-02 Thread Jack
Hello Francois, I've uploaded the project here: http://chatsvr.no-ip.org/download/ProxyTester.zip It was created with Delphi 2005. I could build it with D5 after deleting the Variant unit from uses clause. If you build it as is, you'll see this (long) line twice: 6/2/2005 10:39:36 AM Access de

Re: Re[2]: [twsocket] Receive result of the first ReceiveStr() calltwice-not resolved

2005-06-02 Thread Francois Piette
No attachement here. But you can provide and URL on some server so that anyone willing to have a look at your code can. If you don't have any server, emailing it will be good also, for me alone. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: "Jack" <[EMAIL PROTEC

Re[2]: [twsocket] Receive result of the first ReceiveStr() call twice-not resolved

2005-06-02 Thread Jack
Hello Francois, Thanks for the quick reply. You are right. I should check in the code. But in this particular test environment, I am receiving HTTP/1.x. This I checked from the log. I looked at the httpcli code briefly yesterday but failed to find the part that parses the http headers (I know it

Re: [twsocket] Non-LineMode Protocol Sending and Receiving

2005-06-02 Thread Francois Piette
> It's easy with LineMode on - ICS only forwards the data on when it > receives a delimeter. But when it's off, it seems as though anything > other than file sends and receives (because you don't really act on the > file stream, you just send or recieve its bytes) proves to be a > difficult task.

Re: [twsocket] Receive result of the first ReceiveStr() call twice-not resolved

2005-06-02 Thread Francois Piette
To avoid difficulties, you should first correctly write your GetHTTPReponseStatusCode function to correctly parse the answer. You should not simply remove "HTTP/1.1" but actually check you really have that string. I'm sure you think you receive data twice while you aren't. You think you receive

Re: [twsocket] E-Mail SmtpCli/MimeDec

2005-06-02 Thread Arno Garrels
DZ-Jay wrote: > On Jun 2, 2005, at 02:29, Arno Garrels wrote: > [snip a lot] >> 1.Line >> >> --010609020500050508040002 >> [..] >> >> MimeDec decodes it to "1.Line" >> I would like to know if it is save to replace the trailing >> by . [snip a lot] > In essence, what that means

Re: [twsocket] E-Mail SmtpCli/MimeDec

2005-06-02 Thread DZ-Jay
On Jun 2, 2005, at 03:13, Michael Preslar wrote: (First time posting to the list, so go easy on me :) ) Welcome! Very good post, so no worries :) To the best of my knowledge, the RFC says that its --(identifier) to start a section and --(identifier)-- to end a section.. To me, MimeDec sho

Re: [twsocket] E-Mail SmtpCli/MimeDec

2005-06-02 Thread DZ-Jay
On Jun 2, 2005, at 02:29, Arno Garrels wrote: Arno Garrels wrote: I'm having problems with the last CRLF in plain mime parts. OE as well as SmtpCli put a CRLF between part content and the closing boundary. MimeDec however reads this extra CRLF as content, so I get corrupted messages. Are there

Re: [twsocket] E-Mail SmtpCli/MimeDec

2005-06-02 Thread Michael Preslar
I'm having problems with the last CRLF in plain mime parts. ... Are there mailers running arround that do not append this 'spacer' CRLF? Mozilla Thunderbird behaves the same, here is an example: Message text: "1.Line" Encoded: [..] --010609020500050508040002 Content-Type: text