Agreed. In fact, I'd rather see something that used, for example, a real layout rather than an anemic snippet of HTML. And a real test would involve something that had lots of assets, to showcase Tapestry's ability to compress, GZip, and encourage browser caching (except that he's running the test with just ab, the Apache Benchmarking tool).
On Tue, Feb 28, 2012 at 8:25 AM, "Ulrich Stärk" <[email protected]> wrote: > Agreed, from a marketing point of view having Tapestry there might be a > good idea. > > From a scientific perspective I highly doubt the results are relevant at > all and thus this comparison is nothing but a waste of time in that > regard. > > For example, measuring requests per second doesn't say anything. OK, some > solutions perform better than others. But that is an implementation detail > and has only partly to do with the framework used. Also it says nothing > about productivity which might outweigh the higher costs for hardware. > > Doing this stuff right is hard. And this is - sadly - another example of > how not to do it. > > Uli > > Am Di, 28.02.2012, 17:01 schrieb Howard Lewis Ship: >> Yes, I mentally billed the couple of hours I spent on it as >> "marketing". It was good to learn how to use SQLLite3 and BoneCP >> together. With a little time, I could make it almost as nice as the >> Hibernate support. What I have is just: >> >> /** >> * Define a DataSource service. >> */ >> public DataSource buildBoneCPDataSource() throws Exception { >> >> Properties props = new Properties(); >> >> props.put("open_mode", String.valueOf(SQLiteOpenMode.READONLY)); >> >> BoneCPDataSource ds = new BoneCPDataSource(); >> ds.setDriverClass("org.sqlite.JDBC"); >> ds.setJdbcUrl("jdbc:sqlite:hello.db"); >> ds.setProperties(props); >> ds.setUsername("n/a"); >> ds.setPassword("n/a"); >> // The test documentation indicates up to about 15 parallel >> requests, so let's make sure there's >> // always a connection ready in the pool. >> ds.setMinConnectionsPerPartition(15); >> ds.setMaxConnectionsPerPartition(20); >> >> return ds; >> } >> >> What would be nice would be if you could inject a per-thread >> Connection as easily as (with tapestry-hibernate) a per-thread >> Session, and that the stack would ensure that the Connection was >> released to the pool at the end of the request. Feels like a little >> tapx library coming on at some point. >> >> On Tue, Feb 28, 2012 at 7:57 AM, Ernesto Arroyo <[email protected]> >> wrote: >>> in fact there is not such a "the best framework" >>> there are some bad ones, as struts1 (ancient) and there are quite good >>> ones, tapestry5, ruby on rails or GWT , and this comparitions have no >>> sense >>> >>> Saludos cordiales, >>> Ernesto Arroyo >>> >>> >>> El 28/02/2012, a las 16:07, Kalle Korhonen <[email protected]> >>> escribió: >>> >>> Did you mean to say "Again, a totally useless marketing effort"? >>> >>> Kalle >>> >>> >>> On Tue, Feb 28, 2012 at 1:11 AM, Ulrich Stärk <[email protected]> wrote: >>>> Again, a totally useless comparison. >>>> >>>> On 27.02.2012 19:15, Kalle Korhonen wrote: >>>>> See >>>>> https://github.com/seedifferently/the-great-web-framework-shootout. >>>>> I don't have time right now to write the T5 test app for it myself but >>>>> it'd be good opportunity to market Tapestry since there are no other >>>>> Java-based framework in it yet. Tapestry would likely perform well and >>>>> it'd be interesting regardless to see how a JVM-based implementation >>>>> would stack up against the alternatives. >>>>> >>>>> Kalle >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
