Dear Arno,
Did you test that in exactly the same environment, same box, both
service or GUI applications, both non or RDP sessions etc.. ?
I tested on the same box, GUI and service. Non RDP, all local desktop
I will provide much more data, I´m preparing a document for you and a sample
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
Hello Eric,
so you are right, sorry about that
You are right here too
Sorry about the confusion
No problem.
Happy to know that I'm still OK.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
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
Hello,
What's new in IQ Proxy Server 3.4.2R
- On single port, IQP now supports 60,000 simultaneous connections
http://www.iqproxyserver.com
Just FYI. With thanks to Eric.
Best Regards,
SubZero
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
From what I could see, ICS uses a lot of WM_USER+n messages range but
the use of these custom messages is not recommended. Instead you
should use WM_APP+n.
http://msdn.microsoft.com/en-us/library/ms644930%28VS.85%29.aspx
The reason to use WM_APP is because WM_USER can conflict with system
SubZero
What's new in IQ Proxy Server 3.4.2R
- On single port, IQP now supports 60,000 simultaneous connections
That is really nice, did you get that by just activating the desktop
interaction flag on?
Eric
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
From what I could see, ICS uses a lot of WM_USER+n messages range but
the use of these custom messages is not recommended. Instead you
should use WM_APP+n.
http://msdn.microsoft.com/en-us/library/ms644930%28VS.85%29.aspx
The reason to use WM_APP is because WM_USER can conflict with system
Eric Fleming Bonilha wrote:
SubZero
What's new in IQ Proxy Server 3.4.2R
- On single port, IQP now supports 60,000 simultaneous connections
That is really nice, did you get that by just activating the desktop
interaction flag on?
I bet that. I only wonder how long this option will be
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,
Yes. Plus I noticed IIS runs as a NETWORK_SERVICE account for this purpose.
On Fri, Aug 13, 2010 at 6:19 PM, Eric Fleming Bonilha
e...@digifort.com.brwrote:
SubZero
What's new in IQ Proxy Server 3.4.2R
- On single port, IQP now supports 60,000 simultaneous connections
That is really
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
22 matches
Mail list logo
