d
see if I can pinpoint the source of the WSAAsyncSelect call.
I greatly appreciate your input.
--
Jon Robertson
Embarcadero Certified Delphi XE Developer
Good programming is 40% experience, 30% skill, 20% RTFM, 10% caffeine, and
5% attention to detail.
--
To unsubscribe or change your setting
Select will fail
for one user but not another?
Thank you so much for any thoughts you have.
--
Jon Robertson
Embarcadero Certified Delphi XE Developer
Good programming is 40% experience, 30% skill, 20% RTFM, 10% caffeine, and
5% attention to detail.
--
To unsubscribe or change your settings for T
On Mon, Sep 6, 2010 at 4:53 AM, Angus Robertson - Magenta Systems Ltd
wrote:
>> But my suggestion has absolutely *nothing* to do with enabling ICS
>> users to magically be able able to use ICS with future versions of
>> Delphi.
>
> Wrong, that is exactly what you said in the root message, that ver
Please, please stop assuming that I'm trying to achieve some kind of
magical "hey, it works!" trick out of a magician's hat.
I already replied to DZ-Jay's concern about "automatically supporting
new versions". Just as there is a lowest version check, there can be
a highest version check too.
If
On Mon, Sep 6, 2010 at 2:02 AM, Angus Robertson - Magenta Systems Ltd
wrote:
> Using old components on newer Delphi releases is always risky, and
> totally unnecessary with ICS since the XE version was available on the
> day of release of XE on both the ICS web site, CodeCentral and the
> companio
My apologies for the continued rant, but I had another thought to share. ;)
On Sun, Sep 5, 2010 at 2:31 PM, DZ-Jay wrote:
> Since a new compiler is an absolute unknown factor, it cannot be assumed to
> be supported by default.
If the only objection to using CompilerVersion is to avoid implying
ents. And then
I started code reviews and testing. When I stopped using VER
constants, the only thing that changed is that I spend a lot less time
maintaining the include file.
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming is 40% experience, 30% skill, 20% RTFM,
sions of
Delphi is not irresponsible. The VER based include files grow
significantly with each new version, since the _UP variables have to
be duplicated so much. The approach I'm suggesting is much cleaner
and takes much less time to maintain when new versions of Delphi are
introduced.
--
> But then again, you must know what you are talking about...
Wow. I'm surprised by the hostility.
Based on your JVCL experience, are you aware of anything that should
be reviewed in ICS for XE support?
Isn't JVCL is a little more dependent on the core VCL components than
ICS is? For the most
ne Delphi
version, rather than VER defines.
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming is 40% experience, 30% skill, 20% RTFM, 10% caffeine,
and 5% attention to detail.
--
To unsubscribe or change your settings for TWSocket mailing list
please
last version.
Whether I wait on the component vendor to update the source, or I
update it myself, that's still wasted time. When maintaining 20
different component libraries (yes, that is too many, but necessary),
it takes way too long to migrate the whole set to the new version of
Delphi.
Jo
NDIF}
{$IFDEF USE_VER210}
// Make your Delphi 2010 defines here
{$ENDIF}
So, when compiling this code for Delphi XE, the code assumes that the
compiler/VCL is compatible with Delphi 2010. In general, a fairly
safe assumption. Delphi 2009 is the one major exception I can think
of where this could have
e (ICS)
> http://www.overbyte.be
>
>
> --
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
--
Jon Robertson
Borland Certified Advanc
TCustomLineWSocket.TriggerSessionClosed does not know in this scenario that
the session is being closed because Abort was called.
I like Francois' idea to implement TCustomLineWSocket.InternalAbort and use
it to clear TCustomLineWSocket's buffer, doing some or all of:
FRcvdPtr:= nil;
That sounds like an excellent solution to this particular situation. So
simple, I'm ashamed I didn't suggest it first. :)
On Sun, Mar 28, 2010 at 2:13 PM, Francois PIETTE
wrote:
> Abort call InternalAbort which do not clear the buffer where
> TCustomLineWSocket store received data to break it i
I sent this a couple of days ago, but I didn't see it come through the
list. My apologies if you received a duplicate message.
-- Forwarded message --
From: Jon Robertson
Date: Fri, Mar 26, 2010 at 12:53 PM
Subject: Unit is already finalized, check your threads!!!
To
cy problems. Isn't the Windows message which
> triggered it taken off the message queue by then? If not, why not?
>
> Greetings
>
> Markus
> --
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://lists.elists.org/cgi-bin/mailman/
exception handler, and
> ASyncReceive exits normally.
>
> * This is bad because the application is now in an unstable state with an
> unhandled exception that it never knew about.
>
>
> 5b. TWSocket Modification suggested by Jon Robertson and I: instead of
> ignoring except
6, 2010 at 4:56 AM, DZ-Jay wrote:
>
> On Mar 26, 2010, at 04:02, Jon Robertson wrote:
>
> > To clarify, OnDataAvailable has received complete data, say:
> > help\n
> >
> > In processing that data, an exception occurs and TWSocket.Abort is called
> to
> >
as able to save my other forms.
I don't remember the IDE giving me the chance to get a stack trace, but it
might have. If it happens again, I'll get a stack trace if possible.
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming is 40% experience, 30% skill
ure out, I
suppose.
On Fri, Mar 26, 2010 at 4:14 AM, DZ-Jay wrote:
>
> On Mar 25, 2010, at 18:33, Jon Robertson wrote:
>
> > Does anyone know why ASyncReceive is swallowing the exception and not
> > calling HandleBackgroundException?
>
> Wow, that was a some time ago. As
On Fri, Mar 26, 2010 at 2:46 AM, Jon Robertson wrote:
> In fact, OnDataAvailable has already been called with the exact same data.
> If OnDataAvailable is called twice with the same data, but the data was only
> received once, I consider that a bug.
>
To clarify, OnDataAvailable
r 26, 2010 at 1:14 AM, wilfried Mestdagh wrote:
> Hi,
>
> It is not a bug, it is by design. The data already received is delivered to
> the application. The application can easy check if it is complete data by
> checking the line end character(s).
>
> --
> mvg, Wilfried
&g
lable again during the Abort.
Thoughts?
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming is 40% experience, 30% skill, 20% RTFM, 10% caffeine, and
5% attention to detail.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.
My service, which communicates using ICS, is "flakey" for some customers.
I've got quite a bit of exception handling and logging, and there was
nothing indicating an exception was occurring.
I finally pinpointed an exception that one customer was getting. I hooked
TWSocket.OnDataAvailable and was
e(Path, CP_UTF8));
end;
I've made this change to the code I just grabbed from SVN and it now
compiles. But I'm not sure that is what you intended to do. :)
Thanks
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming is 40% experience, 30% skill, 20% RTFM, 10%
> I changed the file naming scheme to the V7 scheme and changed a few "char
in []" to "CharInSet()".
> I think those were the only changes. These demos work great for me in
D2009.
Argh, it just dawned on me that the CharInSet changes will only work with
D2009. Anyone else should change that back
r demo projects use.
I zipped the source and put it on my (daughter's) website. It is only 13K,
but I didn't want to send 13K to the whole list. :)
http://www.delaneyjoi.com/files/OverbyteIcsTcpCmd.zip
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming
anymore.
By simply changing the WSocket* unit references and replacing "char in []"
with "CharInSet", my TTcpDaemon compiles cleanly. It is a little too early
to know how well it'll work.
I'm just curious if there is some reason I shouldn't use it anymore. Thanks
On Wed, Sep 24, 2008 at 10:59 AM, Francois PIETTE <[EMAIL PROTECTED]
> wrote:
> btw: It is probably a better idea to make the small effort to migrate your
> application to ICS V6 which is available from the SVN server with SSL
> already included. ICS-V5 is in end of life.
>
I'm assuming that if w
ct anyone new to
ICS-SSL would have problems. :D
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
Good programming is 40% experience, 30% skill, 20% RTFM, 10% caffeine, and
5% attention to detail.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http
31 matches
Mail list logo
