[Stackless] Fwd: endian issues pickling tasklets

John Tantalo john.tantalo at gmail.com
Sat Nov 4 16:42:09 CET 2006

That's essentially what we're doing, minus the load balancing,
security, and failover. The first is not a new problem. Security in
this context would be difficult to achieve, since we must also send to
the client the module that contains the tasklet's function. Right now,
we are doing this by storing the module's bytecode, but I'm no python
security expert, so this may not be the best solution. Security is not
a big concern of ours, anyway. As for failover, though we don't have a
mechanism in place, it would be trivial to rollback a failed state to
some previous state, since the entire state history is stored in the
database. Our focus is on the scheduler (broker) and user interface.

- John

On 11/3/06, Grant McDonald <gmcdonald at infocomp.com> wrote:
> It's a very interesting concept, you could think of it as a simple
> architecture on which to build grid services.  All you would need to do
> would be to put a broker architecture around it, some load balancing,
> failover and security and poof! Stackless does grid computing! :)
> Chris: I have been meaning to ask how far has stackless come in PyPy? What
> are it's features compared to the standalone stackless implementation?
> Grant M.
> -----Original Message-----
> From: stackless-bounces at stackless.com
> [mailto:stackless-bounces at stackless.com] On Behalf Of
> Christian Tismer
> Sent: Saturday, 4 November 2006 1:12 AM
> To: Steve Holden
> Cc: stackless at stackless.com
> Subject: Re: [Stackless] Fwd: endian issues pickling tasklets
> Steve Holden wrote:
> ...
> > But "obvious" has different values for different individuals, Christian.
> > Anyway, I've given this a little further exposure at
> >
> http://holdenweb.blogspot.com/2006/11/stackless-python-continues-to-amaze.html
> I agree that the value of "obvious" is obviously not obvious.
> Thanks for this nice blog entry. You are right, there is more
> unused potential around than we thought and should use.
> cheers - chris
> --
> Christian Tismer             :^)   <mailto:tismer at stackless.com>
> tismerysoft GmbH             :     Have a break! Take a ride on Python's
> Johannes-Niemeyer-Weg 9A     :    *Starship* http://starship.python.net/
> 14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
> work +49 30 802 86 56  mobile +49 173 24 18 776  fax +49 30 80 90 57 05
> PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
>       whom do you want to sponsor today?   http://www.stackless.com/
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless
> Important notice: This message is intended for the individual(s) and
> entity(s) addressed. The information contained in this transmission and any
> attached, may be confidential and may also be the subject of legal
> privilege, public interest immunity or legal professional privilege. Any
> review, retransmission, dissemination or other use of, taking of any action
> in reliance upon this information by person or entities other than the
> recipient is prohibited and requires authorization from the sender. If you
> are not the addressee indicated in this message (or responsible for delivery
> of the message to such person) you may not copy or deliver this message to
> anyone. In such cases you should destroy this message and kindly notify the
> sender by reply email.
> WARNING: Although Infocomp has taken reasonable precautions so that no
> viruses are present in this e-mail, the company cannot accept responsibility
> for any loss or damage arising from the use of e-mail attachments.
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless

Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list