I don't know how it would become easier by GWT including such a framework - you will still have to use it correctly. You mean, that the GWT team would be very good at creating a better framework than the ones already that already exist - ok, you may be actually right. But it would still be a separate project I guess (maybe there is already one?)
Database access is also something that is used by almost every web application. You can use JDBC, Hibernate, JPA, JDO, whatever you want. The basic question is: What's the advantage of it being a part of GWT? Would it be sufficient to you if the GWT team suggested the "best" framework to use? On Mar 5, 7:06 pm, Marley <[email protected]> wrote: > > For servers from other vendors, use their security mechanism, or any good > > server side framework. > > Which is what i am asking for...GWT should include an Authentication/ > Authorization framework, as security is needed by most all web > applications. Authentication/Authorization is currently treated as an > afterthought rather than being baked into the framework, and it is > painful to do "right". -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
