<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=247185211-27102005>Hi
all.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=247185211-27102005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=247185211-27102005>I am about to
develop an app that will act as an http gateway for some of the services we are
running. For the incoming http requests I plan to use httpd from
inets. For the outgonig leg it would thus make sense to use the http
client from inets.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=247185211-27102005>My question is
wether any one else is using the inets http client for medium to high volume
outgoing traffic? I know of two instances where people chose to create a
java node to make http connections, instead of using inets.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=247185211-27102005>Is it worth the risk
to try the inets solution first, or should I budget the time to make a java node
and try to upgrade to inets later?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=247185211-27102005>Any one with
experience in this regard?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=247185211-27102005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=247185211-27102005>The requirements for
the http client will be that many connections will be made to a series of
speciffic URLs.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=247185211-27102005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=247185211-27102005>-]-[einrich</SPAN></FONT></DIV></BODY></HTML>