> Anyway, I think there will be a big market for application on Linux
> when it gets more market share, on desktop and servers. Having ICS and
> Pascal available to us would make it a lot easier to code on that
> platform since we are used to Delphi.
Surely. But who do you think has to pay the bil
Also there's a problem with the "Linux Attitude": they've only ever
heard of "source compatibility", no such thing as "binary
compatibility". Even the "source compatibility" leaves a lot to be
desired (did you know Linux has something called "autoconf"? why do you
think they do that?).
IMO, un
I cannot get the Httptst demo working with ContentCoding
and some URLS like:
http://msdn2.microsoft.com/en-us/library/ms737582.aspx
(OnDocData never triggers, display memo empty, local file
ms737582.aspx has zero length)
My settings seem to be OK since a few other links work well
like: http://port
> When evaluating what way to go I thought that either Kylix could be used
> (but is that product still active?) or we port the code (including ICS)
> to C/C++. Maybe the glib library could be used to provide the Unix
> alternative to messages and threads:
> http://www.gtk.org/api/2.6/glib/index.ht
Fastream Technologies wrote:
> Perhaps the TCP connection has some end-to-end keep-alive packets
> sent which does not leave the stream "idle"?
It's no problem to work around by sending NOOP packets,
and/or by implementing a custom time-out in the application protocol.
Only it's annoying to spend
- Original Message -
From: "Tobias Rapp" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Friday, March 02, 2007 3:33 PM
Subject: Re: [twsocket] Project proposal
>I would be very interested if you start this project as my company also
> thinks that in the future it might be interesti
Perhaps the TCP connection has some end-to-end keep-alive packets sent which
does not leave the stream "idle"?
Regards,
SZ
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Friday, March 02, 2007 3:36 PM
Subject: Re: [twsocket] Don't trust r
It's an idle time-out yes.
Fastream Technologies wrote:
> We -in our code- implement/interpret a connection timeout as "idle
> timeout". Could this be the case in Lancom as well?
>
> Best Regards,
>
> SZ
>
> - Original Message -
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS supp
I would be very interested if you start this project as my company also
thinks that in the future it might be interesting to port some of our
Windows service applications to GNU/Linux.
When evaluating what way to go I thought that either Kylix could be used
(but is that product still active?) or w
We -in our code- implement/interpret a connection timeout as "idle timeout".
Could this be the case in Lancom as well?
Best Regards,
SZ
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Friday, March 02, 2007 2:31 PM
Subject: [twsocket] Don'
i.e. Lancom, I was told that it has an option ConnectionAge to specify
a connection time-out. According to the manual the connection will be
closed when the timeout expires. But nothing like that happened. Instead,
after the time-out expired a client application happily sent data that
was never ack
11 matches
Mail list logo
