> > 1) Steal a couple of ideas/features from seaside ( http://seaside.st/ ). > Such as, and this is mostly from memory, session management that handle > * forking of page state due to opening a new window > * forward and back broswer buttons roll the session state forward and > back along with the window display. > > To see why this could be important take a look at one of the shopping > cart/e-commerce demos which I can't seem to locate at the moment. so try > the examples from http://seaside.st/about/examples Having not looked at > seaside for a while the Halos don't look like a bad idea either.
I confess that I've only looked briefly at Seaside. Its features made sense to me in the context of its overall design (no meaningful URLs, server-based continuations) but it didn't click to me how to use these features in a REST-ful framework like ErlyWeb. I think it would be possible to keep a bunch of stateful 'ewc' tuples in Mnesia and modify them using on anchor-triggered continuations, but this is just a very rough of how it might work -- and I'm not sure it would work very well. Having said that, if someone wants to take a crack at it, I'll be happy to let them check in their changes if they are useful. > > 2) Better distribution support out of the box. One of the things which > Erlang makes easier is distributing an app or set of apps across > multiple node yet erlyweb doesn't take advantage of this to date. What I > specifically interested in is redundancy so that should one server fail > for whatever reason the user will not notice, but this could equally > apply to load balancing. There are ways of doing this with linux-HA, > etc, but I think this is something better handled by the webserver > directly for various reasons. Parts of this may be better done as a > spin-off project. Without having done it, I think this would be pretty easy -- keep session data in Mnesia and replicate the table across nodes. If a server goes down, other servers will maintain the same state and you could just route traffic to them. However, I think that unless you're building a banking application or something, occasionally losing session state due to a server crash isn't such a big deal. Most webapps don't need to worry about it too much. What I think would be useful is an automated deploy script that checks out the latest code from the repository and deploys it across a cluster of ErlyWeb servers (without restarting them, of course :) ). However, this kind of project is generally best done out of concrete rather than hypothetical needs -- there are always some details that you would miss unless you actually need this feature in your production environment. Is anyone out there running an ErlyWeb cluster by any chance? :) Thanks, Yariv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
