Hello Francois,
V5 is very stable. It stay existing, and support may not be dropped the
first time, but new users and new projects should start to use V6. So
this way it is not direct problem.
However I'm not 100% sure myself of what I say :)
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/e
Hello Miha,
Very good idea. It is even possible to have more / other methods /
properties / events in the new generation while the old generation stay
backward compatible !
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Thursday, December 29
Hello Angus,
It has happened but almost never in compare with other vendors. Another
example is the BannerToBusy property changed to BannerTooBusy, but it is
very minor work alwasy, wich I cannot say from many other component
vendors.
I think it is strong in ICS the backward compatibility. A shor
> I do not agree with you. I can't say it never happened, but it was
> very uncommon that any change in ICS required _application_ code
> change.
The most recent example is SSL, the versions in the last few months
required numerous application changes over the original implementation,
it's all
> All in all I wonder if it is not better to simply make V6 as
> compatible as possible with V5. That is dropping support for
> old compilers (this would make the source code much cleaner)
> and adding new features without breaking existing ones. If I
> do that, current ICS user would have no c
Hello,
Excellent idea so you can use either TWSocket or TIcsSocket as you
want !
>> Rename classes as wanted ie. TWSocket to TIcsSocket (or using
>> any other prefix), then create proxy unit like below.
>> type
>> TWSocket = class(TIcsSocket);
FP> What a good idea ! I wonder how I didn't ha
>> Many component vendors or ICS competitors always to a lot of changes
>> between versions. ICS never done that and it is one major strength of
>> ICS.
> This is partially a myth, because property changes in new ICS versions
> often mean changes in applications, even if the class names are the sa
> Rename classes as wanted ie. TWSocket to TIcsSocket (or using
> any other prefix), then create proxy unit like below.
> type
> TWSocket = class(TIcsSocket);
What a good idea ! I wonder how I didn't had it myself :-)
--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
> Many component vendors or ICS competitors always to a lot of changes
> between versions. ICS never done that and it is one major strength of
> ICS.
This is partially a myth, because property changes in new ICS versions
often mean changes in applications, even if the class names are the same.
> Can you say some that are not available on D5?
D6 has 64-bit streams and some new functions.
D7 adds nothing new, but there are compiler changes relating to other
platforms.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/l
> I have not taken the final decision yet.
> I'm still grabbing other's opinion.
Rename classes as wanted ie. TWSocket to TIcsSocket (or using any other
prefix), then create proxy unit like below.
a) It would have some sort of redirection from old types to new types:
unit IcsProxyV5;
type
TWS
Francois PIETTE a écrit :
>>That seems to be nicer. But for those who are still working with old
>>compilers, that wouldn't do it.
>>Except if you make the old versions available (leaving a place where to
>>download the V5).
>
>
> I don't plan to delete V5 ! It will stay there for download.
i di
> Using sysinternals tools, it show each connected socket use in 3
> handles :
>
>1 Event
>1 File \Device\Tcp
>1 File \Device\Afd\Endpoint
>
> I don't know what \Afd\EndPoint is nor the unnamed Event.
In my opinion, those handles are created by winsock itself for his
>> I'm still wondering.
>> Renaming everything and cleaning up thing is of course very interesting
>> for
>> new users. But for existing users, it would require a lot of work
>> converting
>> their old code to the new versions. And that may be fatal to ICS: current
>> user would not upgrade to ne
SetWindowLong.
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, December 28, 2005 3:35 PM
Subject: Re: [twsocket] ICS V6 beta available
>> Does this version includes my fix in WSocket?
>
> Which fix ?
>
> --
> [EMAIL PROTECTED]
Hello Francois,
Using sysinternals tools, it show each connected socket use in 3
handles :
1 Event
1 File \Device\Tcp
1 File \Device\Afd\Endpoint
I don't know what \Afd\EndPoint is nor the unnamed Event.
Regards.
>> Seems that 1 connected user eat 3 handles...I w
Francois PIETTE a écrit :
> I'm still wondering.
> Renaming everything and cleaning up thing is of course very interesting for
> new users. But for existing users, it would require a lot of work converting
> their old code to the new versions. And that may be fatal to ICS: current
> user would n
>> I wonder if I should also change all class names. For example rename
>> TWSocket to TOverbyteIcsSocket or TIcsSocket. This way, ICS component
>> would be clearly identified. This of course would require a lot of
>> changes in
>> existing applications, including in dfm.
> I'm not fully against
Hello Francois,
So TIscSocket should be ok because TOverByteIcsSocket is too long :-)
FP> Not better. A component name need a prefix, not a suffix.
FP> TIcsSocket or TIcsWSocket or TOverbyteIcsSocket or...
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://ww
> But I'm also not sure if this is good solution
I'm still wondering.
Renaming everything and cleaning up thing is of course very interesting for
new users. But for existing users, it would require a lot of work converting
their old code to the new versions. And that may be fatal to ICS: current
Maurizio Lotauro a écrit :
> Scrive Francois PIETTE <[EMAIL PROTECTED]>:
>
>>I plan to support Delphi 7, Delphi 2006 (Win32 and .NET) and C-Builder 2006
>>only.
>>Any tought ?
>
> I'm still using D5. I planned to migrate to D7 but probably this will not
> happen before middle 2006 because lack
21 matches
Mail list logo
