> I don't get it: > What exactly makes you ask this question? > How do you get the idea that a database might be of any help? >
Well I was referring to the example of WS-BPEL where time span is is so huge (in days or weeks), I guess storing the state in a DB would be a better option IMHO. I agree with Andrew when he said, pickling can be compared to swap operation of OS. And yes, as others have pointed out these needs to tested properly to figure out time taken for serialization and de-serialization and compare it with DB read and write, specially when load is high and data size is large. --Rana On Fri, Mar 27, 2009 at 5:27 PM, Christian Tismer <[email protected]>wrote: > On 3/26/09 8:29 PM, Rana Biswas wrote: > >> In the world of WS-BPEL, a transaction can take *days* or *weeks* to >> occur (imagine in reality, a product is back-ordered or you are >> waiting for M out of N vendors to respond). For the moment, let us >> put aside issue of what sort of underlying protocol is used. In >> these situations, you would want, after a certain amount of time, to >> pickle the tasklets that constitute the process and free up memory. >> When the message comes back in, depickle the tasklets and they will >> resume where they left off. >> >> >> Won't saving the data in a database be a better idea in this scenario. >> > > I don't get it: > What exactly makes you ask this question? > How do you get the idea that a database might be of any help? > > > -- > Christian Tismer :^) <mailto:[email protected]> > 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 [email protected] http://www.stackless.com/mailman/listinfo/stackless
