<div dir="ltr"><div><div><div><div><div><div><div>Sven, <br><br></div>thanks for the comments. I understand all.<br><br></div>Could you please clarify this:<br><br>"<i>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</i>."<br><br></div>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?<br><br><br></div>Answering on how it goes:<br><br></div>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. "<b>Space is low</b>" warning window appeared. I've clicked on "Proceed" just for curiosity but no reaction in the Pharo gui... hmmm...<br><br><br></div>thanks<br></div>Robert<br><br><div><div><div><div><br><div><br></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-18 13:27 GMT+01:00 Sven Van Caekenberghe <span dir="ltr"><<a href="mailto:sven@stfx.eu" target="_blank">sven@stfx.eu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On 18 Jan 2016, at 13:17, Robert Kuszinger <<a href="mailto:kuszinger@giscom.hu">kuszinger@giscom.hu</a>> wrote:<br>
><br>
> Sven,<br>
><br>
> 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?<br>
<br>
Yes, one of several used by Zn to protect itself from resource abuse (DOS). The default limit is 16Mb.<br>
<br>
> 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.<br>
<br>
The limit you are running into is called #maximumEntitySize and can be set with ZnServer>>#maximumEntitySize: - The default limit is 16Mb.<br>
<br>
Given an adaptor instance, you can access the server using #server.<br>
<br>
So together this would be<br>
<br>
ZnZincServerAdaptor default server maximumEntitySize: 300*1024*1024.<br>
<br>
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.<br>
<br>
Let me know how that goes.<br>
<br>
> thanks<br>
> Robert<br>
><br>
><br>
> 2016-01-18 12:45 GMT+01:00 Sven Van Caekenberghe <<a href="mailto:sven@stfx.eu">sven@stfx.eu</a>>:<br>
> Robert,<br>
><br>
> If you are using Pharo, it seems more logical that you would use ZnZincServerAdaptor.<br>
><br>
> But of course, it might not necessarily have to do with the adaptor.<br>
><br>
> HTH,<br>
><br>
> Sven<br>
><br>
> _______________________________________________<br>
> seaside mailing list<br>
> <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" rel="noreferrer" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" rel="noreferrer" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br></div>