Last time I mailed the list, I was inquiring about implementing a custom
connector or something along those lines to support a binary protocol along
with HTTP. This approach proved flawed for various reasons, if not virtually
impossible to do with the connector, processor, handler architecture e
ended recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Mon, 8 Sep 2008 06:50:19 -0700
> From: [EMAIL PROTECTED]
> Subject: Piggybacking HTTP with binary protocol
> To: users@tomcat.apache.org
>
> Last time I mailed the list
Darryl,
One thing I might suggest is instead of rolling your own http
client; is to use the http client from apache http://hc.apache.org. I
use it myself for various projects including binary data transfer. It
will let you focus on your protocol instead of having to implement
http.
Raymo
eaner, and hardware is cheap cheap these days.
But I will have a look at the Apache client nonetheless.
Thanks,
Darryl
- Original Message
From: Raymond Kroeker <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Tuesday, September 9, 2008 5:41:20 PM
Subject: Re: Piggybacking HTTP with
On Tue, Sep 9, 2008 at 1:10 PM, Darryl Pentz <[EMAIL PROTECTED]> wrote:
> Thanks for that suggestion - I'll definitely look into it. In the meantime
> what we've done is to solve our problem in the hardware, by using 2 network
> cards (i.e. 2 IP addresses)
Uh, you don't need multiple NICs to h
Piggybacking HTTP with binary protocol
On Tue, Sep 9, 2008 at 1:10 PM, Darryl Pentz <[EMAIL PROTECTED]> wrote:
> Thanks for that suggestion - I'll definitely look into it. In the meantime
> what we've done is to solve our problem in the hardware, by using 2 network
> cards
ryl Pentz <[EMAIL
> PROTECTED]>
> Sent: Tuesday, September 9, 2008 9:25:07 PM
> Subject: Re: Piggybacking HTTP with binary protocol
>
> On Tue, Sep 9, 2008 at 1:10 PM, Darryl Pentz <[EMAIL PROTECTED]> wrote:
>
>> Thanks for that suggestion - I'll definitely look
