Does Resin 4.0 have any notion of handling a situation where a large HTTP
MULTIPART POST request has come in (a large file transfer for example), and
then when one of the nodes of the cluster that is handling that MULTIPART
POST were to go offline, another node would take over with no interruption
On 02/22/2012 11:08 AM, Aaron Freeman wrote:
Does Resin 4.0 have any notion of handling a situation where a large HTTP
MULTIPART POST request has come in (a large file transfer for example), and
then when one of the nodes of the cluster that is handling that MULTIPART
POST were to go offline,
-Original Message-
From: resin-interest-boun...@caucho.com [mailto:resin-interest-
boun...@caucho.com] On Behalf Of Scott Ferguson
Sent: Wednesday, February 22, 2012 1:17 PM
To: resin-interest@caucho.com
Subject: Re: [Resin-interest] Resin 4.0 Clustering and HTTP MULTIPART
On
Thanks. I will come up with an alternative.
Rachel
On Wed, Feb 22, 2012 at 3:27 PM, Scott Ferguson f...@caucho.com wrote:
**
On 02/22/2012 02:32 PM, Rachel McConnell wrote:
For various reasons too annoying to detail, it may be useful for us to
change one minor behavior of the
