workers2.properties is for the jk2 connector and workers.properties is for the jk 
connector, they have slightly different syntax I think but you'd best look up the 
jakarta site for that.

Ta
Matt

-----Original Message-----
From: Kommuru, Bhaskar [mailto:[EMAIL PROTECTED]
Sent: 26 May 2004 09:43
To: 'Tomcat Users List'
Subject: Worker2.properties VS Workers.properties


Can any one please explain what is the difference between Worker2.properties
VS Workers.properties? I could not understand that.


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 10:40 AM
To: Tomcat Users List; QM
Subject: Re: HTTP Servlet - How to use the same connection for GET URL?


Hi,
Thanks for replying me!
Unfortunatly the HTTP call is the only way I have to submit my
information...
Ideal would be to send a POST HTTP to tht URL with the same connection, I
mean 
the same socket where the HTTP service is up. The strange is that using a
php 
program, I can POST the HTTP using the same connection for all my requests. 
But I have to use the HTTP Servlet in stead of this php program. I believe 
that the performance of my machine will increase if I avoid a huge amount of

sockets connected/disconnected.

Can any one help me?

Citando QM <[EMAIL PROTECTED]>:

 On Tue, May 25, 2004 at 12:28:04PM +0100, [EMAIL PROTECTED]
 wrote:
 : I have an HTTP Servlet that treats somes information and then make a 
 : GET URL with that information, the problem is that everytime the HTTP
 Servlet 
 : is requested to treat the information and then do a GET URL I'm opening a
 new 
 : connection to that URL and than close the connection. So if I have 10000 
 : requests I will open and close about 10000 sockets to GET the URL. Is
there
 a 
 : way to avoid this?
 
 If I understand your question, there's no good way around this if you
 *must* use an HTTP call.  HTTP is all about stateless, quick-hit
 requests, and it sounds like you're aiming for more of a stateful,
 constant-connection protocol.  Furthermore, if you're opening
 connections to different hosts each time, then reusing the same socket
 is moot anyhow.
 
 Is it a requirement that you perform an HTTP call?  Could you get this
 information, say, from a database?
 
 -QM
 
 -- 
 
 software  -- http://www.brandxdev.net
 tech news -- http://www.RoarNetworX.com
 
 
 ---------------------------------------------------------------------
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 



__________________________________________________________
Quanto gasta de Acesso à Internet? Faça as contas!
http://acesso.portugalmail.pt/contas

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________________________________________________________________________________________________________

For information about the Standard Bank group visit our web site 
<www.standardbank.co.za>
__________________________________________________________________________________________________________________________________
        
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relating to the official business of 
Standard Bank Group Limited  is proprietary to the group. 
It is confidential, legally privileged and protected by law. 
Standard Bank does not own and endorse any other content. Views and opinions are those 
of the sender unless clearly stated as being that of the group. 
The person addressed in the e-mail is the sole authorised recipient. Please notify the 
sender immediately if it has unintentionally reached you and do not read, 
disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been 
maintained nor that it is free of errors, virus, interception or interference.
___________________________________________________________________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to