Yariv Sadan wrote: > I think there many reasons to pick ErlyWeb over Rails besides speed: > > - Concurrency. There are many ways you can use concurrency in your > webapp both to enable new features (e.g. comet, which you have to be > insane to try with Rails) and to improve existing ones (do things in > parallel or in the background to improve page load times). I think the > area of concurrency in webapps is relatively unexplored because most > web developers use languages that make using concurrency too > hard/impractical/unscalable. With ErlyWeb you have a green field of > exploration in front of you. (Here's something I ran into recently: in > a Facebook app, instead of updating user's profile FBML or feed or > sending notification in the same flow as the controller action, you > can spawn those actions into different processes to get faster > perceived response time. It's pretty cool I think. Don't try it with > Rails.) >
Here's a scenario I'm looking forward to: Start a pool of Python nodes for complex image processing using Python Imaging Library When images are uploaded, queue them for processing in the pool, return to the user There are other interesting scenarios where ErlyWeb can easily defer processing to some node/suprevision tree running in the background and return to user immediately without having to wait indefinitely long for a process to finish. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
