It's funny that you say that.
A few months ago when I started to mess around with Tapestry I began to build a Tapestry based Petstore, not in the "Sun way" but in "Microsoft way", I was getting pissed off by my co-workers constant nagging and MS worshiping "Look how cool is ASP.NET" ... "You can be so much more productive with NET"... well to make a long story short I decided to show them that there is more to RWD (Rapid Web Development) than ASP.NET. What do I mean by the "Microsoft way" .. well.... no EJB's of course (I wouldn't know how anyway) and with a slick presentation framework. Tapestry was the only thing that measured up to the challenge. So I started to develop the Tapestry-Petstore targeting MS-SQLServer and PostgreSQL with the goal of giving it back to the community. Unfortunately I was involved in a car crash and I was out of commission for about 2 1/2 months. I just now resumed work in the Tapestry Petstore, mainly bringing it up to Tapestry 2.2. compliance. I'm nearly finished, It just have to implement the OrderConfirmation stage, create a Portuguese localized version , finish the personalization components, and fix some weird bugs (for some reason I'm can't validate forms anymore) You all can see what I'm talking about here: http://213.22.97.4:8080/petshop/estore (This is my home machine, I will only have this here for a while) How does Tapestry compare with ASP.NET? Well ... in my opinion and after working with both for some time (more time with Tapestry) I have to say that **to me** Tapestry is better in all ways but tree: -Performace - Tapestry performs really well over low and medium loads... but when the users start pouring performance degrades terribly. In high loads ASP.NET runs circles around Tapestry... to me this is not problematic I mainly develop Intranet applications and Tapestry is more than fast enough, to others i don't know ... some of my MS worshipers colleagues just like the cool factor that comes with the performance superiority -Integrated components - Not a biggy in my opinion... and the situation is getting better for Tapestry -Client Interaction - Again things are changing in the Tapestry world, but there are some cool thing that ASP.NET does like producing different HTML to accommodate different browsers. The "code weight" as you call it is very similar, i.e, very small in both frameworks. I you feel that you must develop a Tapestry Petshop, then go ahead, I personally think that your time and skills would be best directed to improve Tapestry and not in frameworks "pissing contests"... leave that to people that don't know any better, e.g: people like me :-) ... but hey ...it's your time. Best regards, Luis Neves On Wednesday 18 September 2002 15:38, [EMAIL PROTECTED] wrote: > I've given some thought to re-implementing Pet Store as > a Tapestry application. > > Keep the backend (EJBs) pretty much unchanged. > Convert database access and Entity EJBs to use McKoi DB. > Replace front-end with Tapestry. > > This might be a bit of effort ... I haven't looked at > the Pet Store beyond a quick glance two years ago. > Although M$ has focused on performance, Sun maintains > that its was proof-of-concept, best-practices, etc. > > I'm actually curious about relative code weight of JSP > vs. M$ WebForms vs. Tapestry. > > Also, does anyone know of an open-source code metrics > tool ... just something that can produce a report of the > number of lines-of-code in a project? ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
