Re: [OT] Play! Framework
Re: [OT] Play! Framework
- Subject: Re: [OT] Play! Framework
- From: Pascal Robert <email@hidden>
- Date: Sun, 13 Mar 2011 21:47:23 -0400
Speaking of performance, one of the reasons I want "clean" URLs is to play with reverse proxy and caching headers. I went to a conference (Confoo, I think we should merge WOWODC with that conference next year...) where they talked about using proxies and using Etags + Cache-* headers to reduce the number of calls to the application server (as with other conferences, they only talked about it in a PHP context...), and I want to see if caching can really reduce load on the server-side of things.
>
> I recently evaluated a couple of these new app servers (for Scala) and i found Play! to be the slowest (in terms of scalability/concurrency)...considerably so.
> In fact i think Play! was slower than WebObjects...[though i can't remember for sure]
>
> IMO the primary motivation customers have for moving off WebObjects is its inability to perform in an increasingly multi-core processor world.
> If i were looking at something other than WO i would choose a platform that is more concurrent not less.
>
> i.e for me there wouldn't be any point in choosing Play! over WO...
>
> On 11/03/2011, at 3:23 AM, Pascal Robert <email@hidden> wrote:
>> I saw a demo of the Play! Framework (http://www.playframework.org) at a conference today, and I must say that it's the first time that I saw something that I really want to try out. It seems like a good mix between Ruby on Rails and WO, so I was wondering if someone else here have tried out that framework?
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden