>> IMO Linux lack both true async socket, and messaging system.
>
> I wouldn't say so. By using fnctl() one can do the following: set a
> socket descriptor F_SETFL - O_ASYNC and possibly F_SETOWN if the process
> receiving SIGIO has to be something else than this one and you have
> truly asynchrono
: Despite being part of the freedb team I only represent myself
unless otherwise noted. Freedb is in no way responsible for my actions or
opinions.
> - Original Message -
> From: "Ari Sundholm" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
>
CTED]
> Sent: Sunday, 4 September 2005 1:23 a.m.
> To: ICS support mailing
> Cc: Erich Kuba
> Subject: Re: [twsocket] ICS for Linux Development
>
>
> Hello Eric, hello everyone!
>
>> locks up (threading). In speaking to Ari Sundholm about this, he
> mentioned
&g
application.
Your assistance will be invaluable albeit on a consulting level
Regards
Erich
-Original Message-
From: Ari Sundholm [mailto:[EMAIL PROTECTED]
Sent: Sunday, 4 September 2005 1:23 a.m.
To: ICS support mailing
Cc: Erich Kuba
Subject: Re: [twsocket] ICS for Linux Development
Hello
p://www.overbyte.be
- Original Message -
From: "Ari Sundholm" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Saturday, September 03, 2005 3:22 PM
Subject: Re: [twsocket] ICS for Linux Development
> Hello Eric, hello everyone!
>
>> locks up (threading).
Hello Eric, hello everyone!
> locks up (threading). In speaking to Ari Sundholm about this, he mentioned
> that the design of the TICSSocket components is a bit awkward and that this
> sort of thing was bound to happen. I fully concur with what he has said,
> and feel that a total rewrite of the
> Therefore, I would like to re-develop the core component (TWSocket) set
> under the Linux platform using Kylix 3. The intention is to build a
> version
> of the core components that is fully compatibly (from an interface
> perspective anyway) with TWSocket and then to donate it back to this
>
