Eric, talking about your shared timer: do you call OnTimer of all attached
objects directly or post WM_TIMER to them? I had though over the same timer
class and that was my idea to broadcast timer signal. I think it'll eliminate
the issue of blocking during loop since PostMessage is
ttimers by the shared timer?
Eric
--
From: Anton S. an...@rambler.ru
Sent: Wednesday, August 18, 2010 10:48 AM
To: twsocket@elists.org
Subject: Re: [twsocket] ICS Message handlers
Eric, talking about your shared timer: do you call OnTimer of all
mailing twsocket@elists.org
Subject: Re: [twsocket] ICS Message handlers
Eric,
I found a problem in our software that is limiting the total ammount
of TCP sockets that I can create.
Did you test that in exactly the same environment, same box, both
service or GUI applications, both non or RDP
Can I send attachment to this group? If not, how do I send?
Eric
Please don't send attachments even if it is possible. Upload to
hotfile.com or some similar service (there is a bunch of them!) like
that and link in your message... all of such services offer you a
delete link which you can use
Eric,
I will provide much more data, I´m preparing a document for you and a
sample program, I´m just curious about this findins, your comments
are really appreciated
It is just important that you compare apples with apples.
Can I send attachment to this group? If not, how do I send?
No,
François
Windows limit the number of windows handles to 10.000. That's why ICS V7
is
designed to use only one handler for a lot of TWSocket so that you can
create a lot of sockets. Which OS are you using which allows creating
1.000.000 handles ?
After more testing, and a clear mind of a new
On 08/12/2010 12:56, Eric Fleming Bonilha wrote:
Since my app can have many handles and I need many sockets, I did
many tests and found that procedure TIcsWndHandler.AllocateHWnd;
create its own windows handle, instead of using classes.allocatehwnd
How does this scheme works?
As I understood
Hi Eric,
I hope you received my reply to you and got everything ok between us. I have
a question for you:
On Fri, Aug 13, 2010 at 4:13 PM, Eric Fleming Bonilha
e...@digifort.com.brwrote:
What I do found is that windows imposes a lesser limit (Less than 2.000
handles) for service applications
://www.overbyte.be
- Original Message -
From: Eric Fleming Bonilha e...@digifort.com.br
To: ICS support mailing twsocket@elists.org
Sent: Friday, August 13, 2010 3:13 PM
Subject: Re: [twsocket] ICS Message handlers
François
Windows limit the number of windows handles to 10.000. That's
I'm still stuck with Delphi 7 at the office, so I don't know if this has
changed during the years. However, looking at the source code of
TIcsWndControl.AllocateHWnd(), it appears that it's still locking the
resource in order to create new handles. My guess is, no.
I think that they lock in
Hi SubZero,
I hope you received my reply to you and got everything ok between us. I
have
a question for you:
I got it, don´t worry, I wasn´t mad, I was just thinking that I was asking
something obvious hehe, I thought that it was a silly question, since I
don´t have much knowlege on how
I will try to make something similar to ICS to reduce the amount of
handles that I will consume in my software, by sharing the handles and
defining different ranges of messages per handle
Reusing the design I've done is very easy. Just derive your class from
TIcsWndControl and override the
Eric,
What I do found is that windows imposes a lesser limit (Less than
2.000 handles) for service applications that runs under LocalSystem
account and do not have desktop interaction,
I did know that services limit the maximum number, but did not know
that interactive services allow more.
François
Reusing the design I've done is very easy. Just derive your class from
TIcsWndControl and override the methods
AllocateMsgHandlers, FreeMsgHandlers and MsgHandlersCount to get your own
messages. See how it is done in many ICS components. very easy.
It is really easy to use and it is
Angus Robertson - Magenta Systems Ltd wrote:
I have already created a class called TSharedTimer, which allows me
to create virtually unlimited number of timers, since they will all
share the same resource, and it is working pretty fine.
Arno already added that functionality to ICS, unit
TIcsThreadTimer is a good choice for 10,000+ of lazy timers,
when accuracy isn't very important.
TIcsTimer is a 'normal' timer that requires a TIcsWndControl instance
to work. There are demos of both in the MiscDemos directory.
What I did was something similar, but not using messages
I
Eric Fleming Bonilha wrote:
TIcsThreadTimer is a good choice for 10,000+ of lazy timers,
when accuracy isn't very important.
TIcsTimer is a 'normal' timer that requires a TIcsWndControl instance
to work. There are demos of both in the MiscDemos directory.
What I did was something similar,
One limitation with such kind of implementation (might not be relevant)
is that the application blocks until entire list of events is processed.
Like iterating over a list of n server clients blocks all clients.
Yes, that is true, but I try not to have long processing in timers, just
routines
Dear ICS Team,
I found a problem in our software that is limiting the total ammount of TCP
sockets that I can create.
The problem that I found is that I can´t create many many instances of
TWSocket, because of its internal message handler (I did many tests), here are
my findinds:
We use
It will be interesting to hear an answer to this...
Thank you,
SZ
On Thu, Aug 12, 2010 at 7:56 PM, Eric Fleming Bonilha
e...@digifort.com.brwrote:
Dear ICS Team,
I found a problem in our software that is limiting the total ammount of TCP
sockets that I can create.
The problem that I
It will be interesting to hear an answer to this...
Thank you,
Why? Is that a silly question? :(
I don´t know how ICS works internally, I´m just wondering what is happening
;)
Eric
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
: Thursday, August 12, 2010 6:56 PM
Subject: [twsocket] ICS Message handlers
Dear ICS Team,
I found a problem in our software that is limiting the total ammount of TCP
sockets that I can create.
The problem that I found is that I can´t create many many instances of
TWSocket, because of its internal
François,
Windows limit the number of windows handles to 10.000. That's why ICS V7
is
designed to use only one handler for a lot of TWSocket so that you can
create a lot of sockets. Which OS are you using which allows creating
1.000.000 handles ?
Windows 7 64bit with 4GB RAM, and it does
No, it is not a silly question--I meant that I would second that question.
SZ
On Thu, Aug 12, 2010 at 8:40 PM, Eric Fleming Bonilha
e...@digifort.com.brwrote:
It will be interesting to hear an answer to this...
Thank you,
Why? Is that a silly question? :(
I don´t know how ICS works
24 matches
Mail list logo
