[Seaside] [Pharo-Seaside] Autoload WWW-documents

[Sebastian Sastre]

We can talk forever of ways to consume resources and crash an image (or a linux kernel or a solaris one) and that would keep people distracted from doing stuff that matters.

I mean, it's okay to experiment and play, but came on man, give some real usage problems

sebastian


On Nov 12, 2010, at 2:02 PM, Marten Feldtmann wrote:

> From my former VA problem I created a simple Component with the two methods:
> 
> renderContentOn: html
>    html text: DateAndTime now printString.
>    html paragraph: 'Hello World from Seaside.'.
>    html paragraph: [
>        html text: 'To learn more about Seaside components follow the link to the book: '.
>        html anchor
>            url: 'http://book.seaside.st/book/fundamentals/rendering-components';
>            with: 'Dynamic Web Development with Seaside'.
>        html text: '.' ].
>    1 to: 10000 do: [ :anIndex | html break. html anchor callback: [ ] ; with: 'www.heise.de'  ].
> 
> and:
> 
> updateRoot: aHTMLRoot
> 
>  super updateRoot: aHTMLRoot.
>  aHTMLRoot meta
>    responseHeaderName: 'refresh' ;
>    content: 1 greaseString
> 
> then I use a chrome with three tabs and after 2 hours the Pharo image (the latest own downloadable) throws an out-of memory exception.
> _______________________________________________
> 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/20101112/5fd293af/attachment.htm