Yariv Sadan wrote: > Also, we should start planning the next release. What features do you > think will be most useful (web services support is on the list)? >
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. 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. Jeff. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
