[Glass] commitOnAlmostOutOfMemoryDuring: within Seaside and not expiring session?

[Richard Sargent via Glass]

It's been mentioned a few times: use a service vm. Then you can do whatever
you want, without being constrained by the seaside rules.
 On Feb 26, 2015 7:38 AM, "Mariano Martinez Peck via Glass" <
glass at lists.gemtalksystems.com> wrote:

> Hi guys,
>
> I am trying to do some export/import using SIXX from the web (Seaside).
> Since the graphs are large, I must use "MCPlatformSupport
> commitOnAlmostOutOfMemoryDuring:".
> However, the problem is that with the first "System commitTransaction" my
> seaside session is kind of expired and redirected to the login page (and of
> course the task doesn't continue).
> I have already had this need in the past...basically...I don't know how
> can I commit yet continue with my seaside session untouched.
>
> Yes, I am using GLASS and it's default transaction management.
>
> Thoughts?
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150226/aa80ef0c/attachment.html>