JRun does not maintain a pool of URL objects. This should be an enhancement
in JRun 4.0.
I'm not quite clear on your requirements description. Separate the applet
and Servlet for a minute. What is it you want to do on the server-side? A
code example would help.
Scott Stirling
> -----Original Message-----
> From: Diego Diego [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 29, 2000 11:56 AM
> To: JRun-Talk
> Subject: RE: URL Connection Cache
>
>
> Brett,
>
> Thank you very much .
>
> I have a applet that talks to a servlet that talks to a http server that
> expects me to hang around and wait for the output
> which could come 5 min or 5 hours later.
>
> 1. The applet opens a connection to the servlet .
> URL("http://localhost/servlet/process?requestid=333")
> (I want the applet to send new requestid without having to open a
> connection all the time)
>
> 2. The servlet opens a connection to the http server and waits for the
> results which can come after one sec and then a new response
> can come in
> 66 mins and so .
>
> 3. The servlet waits for response and foward it to the right
> clients who is
> waiting.
>
> Maybe you can suggest a better way of getting this done with out keeping a
> connection open per request.
>
> Diego
> Punta Gorda, Belize
~~~~~~~~~~~~~ Paid Sponsorship ~~~~~~~~~~~~~
Get Your Own Dedicated Win2K Server! Instant Activation for $99/month w/Free
Setup from SoloServer PIII600 / 128 MB RAM / 20 GB HD / 24/7/365 Tech Support
Visit SoloServer, https://secure.irides.com/clientsetup.cfm.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
