[Seaside] ZINC - Kom dilemma Fwd: WADebugErrorHandler problem

Robert Kuszinger kuszinger at giscom.hu
Mon Jan 18 12:39:29 UTC 2016


Sven,

thanks for the comments. I understand all.

Could you please clarify this:

"*Technically, it would be possible to write a Zn handler that can accept a
large upload in a streaming fashion (and save it to a file for example),
but I don't think that will happen with Seaside - so you will pull that all
in memory*."

Is there a chance to create a streaming solution? Is it documented
somewhere? Why do you think it won't happen with Seaside? Is there a
Seaside set or design limitation?


Answering on how it goes:

20 - 40 - 10MB upload in seconds. Now it seems to stuck on a ~ 120 MB
upload. Pharo memory (windows OS) seemed to grow ~ 441 MB. "*Space is low*"
warning window appeared. I've clicked on "Proceed" just for curiosity but
no reaction in the Pharo gui... hmmm...


thanks
Robert




2016-01-18 13:27 GMT+01:00 Sven Van Caekenberghe <sven at stfx.eu>:

>
> > On 18 Jan 2016, at 13:17, Robert Kuszinger <kuszinger at giscom.hu> wrote:
> >
> > Sven,
> >
> > thanks for the tip. Actually the UTF problem won't appear with Zinc but
> I also need to do large file uploads. Zinc resets connection somewhere
> between 10-19 MB File size. Is there a built-in limitation?
>
> Yes, one of several used by Zn to protect itself from resource abuse
> (DOS). The default limit is 16Mb.
>
> > Anyway, an idea on how to break through this limit may also help. I need
> to upload 150-300 MB files regulary with this service. KomHttp did it
> out-of-the-box.
>
> The limit you are running into is called #maximumEntitySize and can be set
> with ZnServer>>#maximumEntitySize: - The default limit is 16Mb.
>
> Given an adaptor instance, you can access the server using #server.
>
> So together this would be
>
>   ZnZincServerAdaptor default server maximumEntitySize: 300*1024*1024.
>
> Technically, it would be possible to write a Zn handler that can accept a
> large upload in a streaming fashion (and save it to a file for example),
> but I don't think that will happen with Seaside - so you will pull that all
> in memory.
>
> Let me know how that goes.
>
> > thanks
> > Robert
> >
> >
> > 2016-01-18 12:45 GMT+01:00 Sven Van Caekenberghe <sven at stfx.eu>:
> > Robert,
> >
> > If you are using Pharo, it seems more logical that you would use
> ZnZincServerAdaptor.
> >
> > But of course, it might not necessarily have to do with the adaptor.
> >
> > HTH,
> >
> > Sven
> >
> > _______________________________________________
> > seaside mailing list
> > seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160118/f5766cbf/attachment.htm


More information about the seaside mailing list