Paul Taylor - Affordable Technology a écrit :
> Hello all,
>
> It's good to see the idea of an ICS Help File gaining momentum. I'm indebted
> to Francois for the number of years that I have used his components and
> would love to give something back. It will be a long-term project and
> keeping up
Jack wrote:
> Hello Francois,
>
> I find that calling pause in OnSessionConnected() is effective.
> But calling pause in OnClientDataAvailable() does not work.
> OnClientDataAvailable() keeps getting fired. Any ideas?
You may have paused the server socket instead of the
TWSocketClient?
Arno Gar
The idea is to build a wiki first and then export the content to other
format.
The wiki is on the way (http://wiki.overbyte.be). Currently it is almost
empty except a few templates and test a small group of volunteers have
setup. Anyone is welcome of course. There is a dedicated mailing list to
> I find that calling pause in OnSessionConnected() is effective.
> But calling pause in OnClientDataAvailable() does not work.
> OnClientDataAvailable() keeps getting fired. Any ideas?
Maybe your socket already received data when you pause it.
Pause only affect winsock notification. It stops noti
I encounter some problems with the HttpCli when a virus scanner is updating
itself.
I think the virus scanner is blocking the internet connection, which results in
errors in the HttpCli.Requestdone event.
It is save to call the Abort method and restart the operation (GetAsync -
PostAsync) immedi
>I encounter some problems with the HttpCli when a virus scanner is updating
>itself.
> I think the virus scanner is blocking the internet connection, which
> results in errors in the HttpCli.Requestdone event.
Which error code do you get ?
> It is save to call the Abort method and restart the
> Which error code do you get ?
Always hard to tell : I get the information from someone on the planet :-(
I've tried to simulate it here, but no luck so far.
Does the Abort method works immediately or is it better to destroy and
recreate the component ?
> It is probably a good idea to wait a
> Does the Abort method works immediately or is it better to destroy and
> recreate the component ?
No need to destroy the component. But before doing something else, wait to
receive the OnrequestDone which will be triggered by Abort (If memory serve
me well).
>> It is probably a good idea to
Can I send directly everytime I call the client.Send(@sf, sizeof(sf))?
Does TWSocketServer have any property that allow me to send everything
without buffered first?
regards,
Widita
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/lis
> Can I send directly everytime I call the client.Send(@sf, sizeof(sf))?
Yes, but pay attention to dynamic data which is represented by pointers.
Sending a pointer to a remote site is useless !
Dynamic data are long strings, objects, dynamic arrays, pointer to
anything,...
> Does TWSocketServer
On 2/19/06, Francois PIETTE <[EMAIL PROTECTED]> wrote:
>
> > Can I send directly everytime I call the client.Send(@sf, sizeof(sf))?
>
> Yes, but pay attention to dynamic data which is represented by pointers.
> Sending a pointer to a remote site is useless !
> Dynamic data are long strings, objects
>>> to send everything without buffered first?
>> What do you mean by "buffering first" ?
> It's something like this, when I send 2 packets consecutively, 1 after
> another, it often received as one packet in the client side
> (WSocket1DataAvailable event)...
This is how TCP stream is operating.
On 2/19/06, Francois PIETTE <[EMAIL PROTECTED]> wrote:
>
> >>> to send everything without buffered first?
>
> >> What do you mean by "buffering first" ?
>
> > It's something like this, when I send 2 packets consecutively, 1 after
> > another, it often received as one packet in the client side
> > (
> Ok, then I must manage the received buffer by myself?
> cutting and joining so that it can be interpreted perfectly by the
> receiver,
> is that right?
Yes and no :-)
TWSocket has a "line mode" in which it assemble (or split) packets for you.
You specify a delimiter (default to #13#10 but can b
- Original Message -
From: "Surabaya" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 19, 2006 5:54 PM
Subject: Re: [twsocket] Sending directly, not via Send Buffer
> On 2/19/06, Francois PIETTE <[EMAIL PROTECTED]> wrote:
>>
>> >>> to send everything without buffere
On 2/19/06, Francois PIETTE <[EMAIL PROTECTED]> wrote:
>
> > Ok, then I must manage the received buffer by myself?
> > cutting and joining so that it can be interpreted perfectly by the
> > receiver,
> > is that right?
>
> Yes and no :-)
> TWSocket has a "line mode" in which it assemble (or split)
Hello Surabaya,
if you send binary with LineMode there are many way to manage it.
The simplest : use BASE64 e-mail attachement style that is nice as
designed to work ascii lined mode but increase size of data about
+40% (as all binary e-mail attachements do by the way).
You could
> I'm going to send binary data, using 5 characters delimiter... is it safe?
Yes, provided your delimiter is not within the data !
If data must contain the delimiter, then you have to escape it.
--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http:/
OK, I'll try the Base64 method
Do you have any recommendation about Base64 encoding/decoding library?
On 2/19/06, Dod <[EMAIL PROTECTED]> wrote:
>
> Hello Surabaya,
>
> if you send binary with LineMode there are many way to manage it.
>
> The simplest : use BASE64 e-mail attachemen
What about Mimeutils.pas in ICS package?
Regards,
SZ
- Original Message -
From: "Surabaya" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 19, 2006 7:42 PM
Subject: Re: [twsocket] Sending directly, not via Send Buffer
> OK, I'll try the Base64 method
>
> Do
Ok, I'll try it thanks...
On 2/20/06, Fastream Technologies <[EMAIL PROTECTED]> wrote:
>
> What about Mimeutils.pas in ICS package?
>
> Regards,
>
> SZ
>
> - Original Message -
> From: "Surabaya" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Sunday, February 19, 2006 7:42 PM
> OK, I'll try the Base64 method
It is more efficient to use a simple escape mechanism.
Let's say your delimiter is #13#10 (this is handy if you test with telnet).
The select another character which is likely to be infrequently use in your
binary data. Let's assume it is #127.
Then it is enou
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 19, 2006 3:57 PM
Subject: Re: [twsocket] Sending directly, not via Send Buffer
>> Ok, then I must manage the received buffer by myself?
>> cutting and joining so that it ca
Yes, right now I am facing the same problem as Dan's
I'm receiving more than one line in a call of DataAvailable
does TWSocket has any property to set so that there will only be a line per
DataAvailable event triggered?
On 2/20/06, Dan <[EMAIL PROTECTED]> wrote:
>
>
> - Original Message -
As far as I know WaitForSingle(/Multiple)Object will block your thread,
and if you are working with a single thread that means it will block you
main thread indefinitely because once blocked you cannot set events or
semnalize semaphores etc..
There are some cases in which OnRequestDone is not c
> Yes, right now I am facing the same problem as Dan's
>
> I'm receiving more than one line in a call of DataAvailable
> does TWSocket has any property to set so that there will only be a line per
> DataAvailable event triggered?
Set :
WSocket1.LineMode := TRUE;
WSocket1.LineEnd := #13#
26 matches
Mail list logo
