Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <54276.146.171.254.66.1223326073.squirrel@www.gera.co.nz>
In-Reply-To: <00ca01c927f4$59de1580$0300000a@animal>
References: <19839078.post@talk.nabble.com>
    <7911FBED-EDD2-4EC0-86F7-354D5E1EA89F@kjkoster.org>
    <00ca01c927f4$59de1580$0300000a@animal>
Date: Tue, 7 Oct 2008 09:47:53 +1300 (NZDT)
Subject: Re: Using tomcat to hold many open connections.
From: ayden@gera.co.nz
To: "Tomcat Users List" <users@tomcat.apache.org>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

Im no techo but I think this is might help
Have a look at icefaces.org
if you can work out how to do it and whats required from tomcat side (NIO
etc) please let me know :)

>
> ----- Original Message -----
> From: "Kees Jan Koster" <kjkoster@kjkoster.org>
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Sent: Monday, October 06, 2008 9:22 PM
> Subject: Re: Using tomcat to hold many open connections.
>
>
>> Dear Uprooter,
>>
>>> I'm looking for a server that has to hold many (web services) remote
>>> clients
>>> for controlling them.
>>> I want to do things like sending power off command to a bunch of
>>> machines
>>> remotely.
>>
>> Building a botnet? :-)
>>
>>> The clients are usually windows machines behind firewalls  NAT or web
>>> proxies that only allow HTTP (this is why I thought of webservices)
>>>
>>> The regular request-response fashion that servlet follows  is not
>>> suitable
>>> here since the initiator of the operation is the server.
>>> What can I do in order to solve this and still use web services?
>>
>> If you have the resources, you can just block in the servlet on your
>> server. It's pretty expensive since Tomcat uses a thread per request I
>> believe. Java threads are expensive (256kB each?), so that adds up
>> quickly. You could spend some time tuning your thread stacks, though.
>> Depending on your actual number of clients, you should be able to get
>> this to work with a few GB of RAM.
>>
>> But then, 20K client polling once an hour might be cheaper. You may
>> want
>> to find a way to stagger the requests though.
>>
>> --
>> Kees Jan
>
> Yes Kees exactly... this is why I say "engineer it"... these guys find a
> hammer, and then everything look like a nail... ha ha
> Without more details we cant engineer it... but I do think, web services
> are
> not the right tool, at most an addendum, not the core... and that there
> are
> two distinct processes at work, web side and machine side... they
> interface
> but cant be combined... to do this right, you got to be a good general
> coder...
>
> ---------------------------------------------------------------------------
> HARBOR : http://www.kewlstuff.co.za/index.htm
> The most powerful application server on earth.
> The only real POJO Application Server.
> See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
> ---------------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org