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
between the client and the cluster?

If not, is there any technology that handles large MULTIPART POSTs in some
redundant form like that?



resin-interest mailing list

Reply via email to