[twsocket] ICS v6 migration considerations

2007-10-17 Thread DZ-Jay
Hello: We have a few applications using ICS v5, mostly written in D2006/7, but some in D5. I would like to move to ICS v6, since that seems to be where major development is taking place, and also because I would like to take advantage of its new hidden window architecture. However, I'm

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Fastream Technologies
v6 IS stable. Yet the "test exception" could be a problem with threaddetach. HTH, SZ > I would also like to hear from users of ICS v6 and whether they find it stable in their production software. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.el

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Olivier Sannier
Fastream Technologies wrote: > v6 IS stable. Yet the "test exception" could be a problem with threaddetach. > Can you elaborate a bit more on this? -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Arno Garrels
DZ-Jay wrote: > Hello: > We have a few applications using ICS v5, mostly written in D2006/7, > but some in D5. D5 won't work, ICS V6 is specified for D7 and better. > I would like to move to ICS v6, since that seems to > be where major development is taking place, and also because I would > like

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Angus Robertson - Magenta Systems Ltd
> Are there any specific issues that I should be aware of before > attempting the switch? I've been using ICS V6 in all my commercial applications now for almost a year, and it is absolutely solid. Migration from V5 to V6 is essentially just changed the Uses names, but one or two more names may

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread DZ-Jay
On Oct 17, 2007, at 06:52, Arno Garrels wrote: > function TFoo.MsgHandlersCount : Integer; > begin > Result := 1 + inherited MsgHandlersCount; > end; > > procedure TFoo.AllocateMsgHandlers; > begin > inherited AllocateMsgHandlers; > FMsg_WM_FOO := FWndHandler.AllocateMsgHandler(Self); >

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Fastream Technologies
Arno claims otherwise but, occasionally after I threaddetach a THttpCli from a worker thread, I get a test exception, which I guess means there are posted messages still left on the message queue... On 10/17/07, Olivier Sannier <[EMAIL PROTECTED]> wrote: > > Fastream Technologies wrote: > > v6 IS

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Arno Garrels
DZ-Jay wrote: > On Oct 17, 2007, at 06:52, Arno Garrels wrote: >> function TFoo.MsgHandlersCount : Integer; >> begin >> Result := 1 + inherited MsgHandlersCount; >> end; >> >> procedure TFoo.AllocateMsgHandlers; >> begin >> inherited AllocateMsgHandlers; >> FMsg_WM_FOO := FWndHandler.A

Re: [twsocket] ICS v6 migration considerations

2007-10-17 Thread Francois PIETTE
> I've been using ICS V6 in all my commercial applications > now for almost a year, and it is absolutely solid. > I have no idea why V6 is still called a beta, this is why > many people refuse to use it. Quick question: Is someone against renaming ICS-V6-BETA as "released" ? Contribute to