--Andrew
On 12/1/05, Andrew Berman <[EMAIL PROTECTED]> wrote:
Honestly, I don't think there ever was a Spring Integration problem. I think people were just looking for a cookie-cutter approach to using Spring within Wicket. It's actually quite easy to do without using any of the Spring stuff that Igor and others wrote, but it's always a good thing to have a common approach that everyone can follow.
As far as session usage, there was an article I read a while ago that actually talked about how developers are not using the session enough. Basically, since a lot of servers have oodles of RAM and disk space, the article's point was that there's no reason not to use the resources available in order to increase speed (not having to go to DB all the time, for example). Obviously, there are a lot of other factors that are involved in session usage, such as number of simultaneous users, but the article certainly made sense. As Eelco pointed out, there are definitely pros and cons, but honestly I don't think Wicket's usage of the session should push anyone away from using it.
--AndrewOn 12/1/05, Iman RahmatiZadeh < [EMAIL PROTECTED]> wrote:>Why? Igor and a couple of others build some pretty decent Spring
>support now? It's all in HEAD, and there has to be a proper build for
>it made, but I think we now have Spring integration that most people
>are happy with.
I'm looking forward to see a real final solution to the spring integration problem, I've
seen most examples about it, and am currently using my own solution in my app,
but just think its time for everybody to agree on the best solution, integrate it into
the core, and stick to it from now on.
And BIG thanks for all the good work !
Iman
