Persistence for Seaside

While browsing for other persistence options, I stumbled over
http://www.visoracle.com/squeak/faq/persistency_.html
How much of that still applies?

Stephan Eggermont
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi!

Stephan Eggermont wrote:
> While browsing for other persistence options, I stumbled over
> http://www.visoracle.com/squeak/faq/persistency_.html
> How much of that still applies?

My guess is that most of it "applies", but I haven't looked it all over.
Btw, thanks for putting that info up at seaside.st - very nice.

I think if you ask specific questions it is easier for us to answer - I
am fairly sure there are other persistence options (more or less
working/incomplete :) ) out there that have not yet been mentioned.

For example, a few loose odds and ends from SqueakMap:

http://map.squeak.org/packagebyname/yates
http://map.squeak.org/packagebyname/persistence
http://map.squeak.org/packagebyname/minnestore

The following are "parts" that can be used in persistence solutions:

http://map.squeak.org/packagebyname/kats
http://map.squeak.org/packagebyname/staterepl
http://map.squeak.org/packagebyname/writebarrier

For example, combining Kats/WriteBarrier (giving image side transactions
and modification discovery respectively) with say TokyoTyrant and some
kind of serialization technique (SmartRefStreams, SRP, JSON whatever)
you could get something interesting. Probably what I intend to play with
further on.

regards, Göran

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

Hi Goran, curious.. that would be multi-image or mono-image?
cheers,
sebastian

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

Nice links. For squeak, there is also this link: http://wiki.squeak.org/squeak/512

Greetings,

Mariano



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

Sebastian Sastre wrote:
Multi. My TokyoTyrant package implements the network protocol so you
would have multiple images running against the same TT server.

Note though (in case you try playing with my TT packagte) that the
latest TT release broke my unit tests, need to look at Mikios changelog
and update.

regards, Göran

PS. At my current assignment we are using CouchDB and that is also a
very, very nice persistence solution.

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

I'm already compromised with a cool solution but having more good options is
always welcome.
This one sounds very promising one that certainly deserves blogging about :)
best
sebastian

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

Göran Krampe wrote: But Kats is in-image so transaction support will only be within a single
image, right?...or does TT have some transaction support that you can
hook Kats into?

David

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

C. David Shaffer wrote:
Right, well, TT does have some transaction support - but I haven't
looked at it yet. Mikio is even adding map/reduce stuff these days. Kats
may perhaps not really be that easily used in this combo, I agree.

regards, Göran

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