Seaside and Exupery patch

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside and Exupery patch

Bryce Kampjes

I've placed Seaside2.8a1-wbk.523 on to the Seaside SqueakSource
repository. This is a patch that moves the serialisation of
contexts from Continuation into ContextPart. This is to allow
Seaside to work with Exupery.

Is it possible to get this merged into the development branch of
Seaside?

Yes, the latest development versions of Exupery will run Seaside, no,
it's not yet practical. Expect bugs and don't expect a performance
improvement yet.

Bryce
_______________________________________________
Exupery mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Exupery patch

Jason Johnson-5
What is the impact of this move?  Is it lesspower then continuations?

On Dec 3, 2007 9:47 PM,  <[hidden email]> wrote:

>
> I've placed Seaside2.8a1-wbk.523 on to the Seaside SqueakSource
> repository. This is a patch that moves the serialisation of
> contexts from Continuation into ContextPart. This is to allow
> Seaside to work with Exupery.
>
> Is it possible to get this merged into the development branch of
> Seaside?
>
> Yes, the latest development versions of Exupery will run Seaside, no,
> it's not yet practical. Expect bugs and don't expect a performance
> improvement yet.
>
> Bryce
> _______________________________________________
> Exupery mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery
>
_______________________________________________
Exupery mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Exupery patch

Bryce Kampjes
Jason Johnson writes:
 > What is the impact of this move?  Is it lesspower then continuations?

It allows ExuperyContext's to deoptimise themselves before they're
serialised.

Otherwise there's a risk that the code cache is cleared while the
continuation is suspended. If it's then re-instated it'll refer to
machine code that may not be there.

The catch is Seaside stores all the state of a context in a collection
then stuffs it back into the context.

There's no catch. Contexts in continuations will be interpreted but
then they're living from web page to web page so are unlikely to need
to be compiled anyway.

Bryce
_______________________________________________
Exupery mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery