Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-06-05 Thread Arno Garrels
Olivier Sannier wrote: >> It's a workaround only, since one hidden window can handle a maximum >> number of const WH_MAX_MSG = 100 registered message IDs only, hence >> it won't prevent ICS from creating new hidden windows on demand >> depending on the number of concurrent client instances. > Yes,

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-06-05 Thread Olivier Sannier
Arno Garrels wrote: > Olivier Sannier wrote: > >>> Thanks for the information. I did moved to v6 and had to adapt a few >>> things (would have been nice if Disposed in TIcsWndControl had been >>> protected and not private) but it did not help at first. >>> Why? >>> Because as soon as all connect

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-06-05 Thread Arno Garrels
Olivier Sannier wrote: >> Thanks for the information. I did moved to v6 and had to adapt a few >> things (would have been nice if Disposed in TIcsWndControl had been >> protected and not private) but it did not help at first. >> Why? >> Because as soon as all connected clients would disconnect, the

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-06-04 Thread Olivier Sannier
Olivier Sannier wrote: > Arno Garrels wrote: > >> Fastream Technologies wrote: >> >> >> >>> Upgrading might be simpler than you think. Just rename ICSv5 folder, >>> unzip and install v6 package and then rename all ICS unit names so >>> that they start with "OverbyteIcs...". >>> >>>

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-28 Thread Olivier Sannier
Arno Garrels wrote: > Fastream Technologies wrote: > > >> Upgrading might be simpler than you think. Just rename ICSv5 folder, >> unzip and install v6 package and then rename all ICS unit names so >> that they start with "OverbyteIcs...". >> > > Indeed it is easy, however if you have derive

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-28 Thread Olivier Sannier
DZ-Jay wrote: > On May 26, 2008, at 09:55, Arno Garrels wrote: > > >> There is a maximum number of user handles, per-process (default 1), >> and system-wide (AFAIK $), so this error seems perfectly OK. >> Maybe your application leaks handles? If not, you may want to try to >> increase th

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-27 Thread DZ-Jay
On May 26, 2008, at 09:55, Arno Garrels wrote: > There is a maximum number of user handles, per-process (default 1), > and system-wide (AFAIK $), so this error seems perfectly OK. > Maybe your application leaks handles? If not, you may want to try to > increase the maximum number of user

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Arno Garrels
Fastream Technologies wrote: > Upgrading might be simpler than you think. Just rename ICSv5 folder, > unzip and install v6 package and then rename all ICS unit names so > that they start with "OverbyteIcs...". Indeed it is easy, however if you have derived classes with overidden WndProc-methods a

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Fastream Technologies
Hi, ICSv6 beta is stable. We have been using it since 2006 and our customers are fully taking advantage of it with hundreds of GBs of serving in months of running... Upgrading might be simpler than you think. Just rename ICSv5 folder, unzip and install v6 package and then rename all ICS unit name

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Arno Garrels
Hello Olivier, > I went further and traced it to the XSocketAllocateHWnd method that > returns 0 when called from the TCustomWSocket.Create constructor for > my client class. There is a maximum number of user handles, per-process (default 1), and system-wide (AFAIK $), so this error seems

[twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Olivier Sannier
Hi all, I have a server here with parts of it written using Indy and parts of it written using ICS. The two parts are distinct, listen on different ports and do not share any resources. Basically, I'm looking at replacing Indy with ICS and would like to have both technologies in one service to

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Fastream Technologies
Yes, Arno is right, I forgot that even though we did those overriding in our codes. Sorry. Regards, SZ On Mon, May 26, 2008 at 6:00 PM, Arno Garrels <[EMAIL PROTECTED]> wrote: > Fastream Technologies wrote: > > > Upgrading might be simpler than you think. Just rename ICSv5 folder, > > unzip and

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Fastream Technologies
Hi, Why don't you upgrade to v6? It was designed for sharing hidden Windows. Best Regards, SZ On Mon, May 26, 2008 at 3:23 PM, Olivier Sannier <[EMAIL PROTECTED]> wrote: > Hi all, > > I have a server here with parts of it written using Indy and parts of it > written using ICS. The two parts ar

Re: [twsocket] "Not enough storage" error in XSocketAllocateHWnd

2008-05-26 Thread Olivier Sannier
Because all my development was made with v5, that I do not want to move to v6 right now as it is still a beta, and that I think there must be something I did wrong to get this error message. Sure, it would be nice to use v6, but it's not possible right now. Fastream Technologies wrote: > Hi, > >