On Jan 11, 2011, at 5:57 PM, Steven Baker wrote:
About 6 months ago I shelved a project for doing Heroku-style deployments from Pharo to Seaside. Perhaps I should dig out my backup and pick it up. I thought I was the only one that might want this, and I got caught up with some issues serializing and sending objects over the network.
I would love to see money raised for doing this kind of startup over pharo.
So that's my first question: what's the best way to serialize and send an object over the network? Would it perhaps be better to just tell the deployed image to use Monticello to update? Can Monticello roll back in case of error (so it can be headless)?
not as far as I know. Now I think that we are making progress to be able to load code in a separate environment so we could really load everything in an environment and not install it in case of problem. It just takes more times than expected. Stef
-Steven
On Tue, Jan 11, 2011 at 6:36 AM, Geert Claes <geert.wl.claes@gmail.com> wrote:
Nick Ager wrote:
there's always EC2 and Gemstone: http://www.vimeo.com/18375790
Yep, I reckon the screencast you made is great ... but ... it's not quite the same though :)
-- View this message in context: http://forum.world.st/PHP-Fog-tp3208657p3209078.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.