As far as I know, there's nothing that prevents the conditionals throughout
the code. Fortunately, with GWT, you're basically coding in Java, so all of
the patterns you're used to for reducing the number of conditionals in your
code should apply in the same way (basically, polymorphism through
Hi,
How do you handle the security/authorizations on GWT layer.
-Aswath
www.AccountingGuru.in
On Wed, Jul 13, 2011 at 5:59 AM, objectuser kevin.k.le...@gmail.com wrote:
If anyone is interested, I've posted a short guide to using Apache Shiro on
Google App Engine:
Well, on the client (browser), there's no security at all. Security (that
is, protecting your site from the user), is impossible. If you just mean
disabling buttons or changing parts of the page, then you can just pass back
permissions to do that. It doesn't guarantee anything, of course.
On Fri, Jul 15, 2011 at 6:43 AM, objectuser kevin.k.le...@gmail.com wrote:
Well, on the client (browser), there's no security at all. Security (that
is, protecting your site from the user), is impossible. If you just mean
disabling buttons or changing parts of the page, then you can just
If anyone is interested, I've posted a short guide to using Apache Shiro on
Google App Engine:
http://objectuser.wordpress.com/2011/06/30/apache-shiro-on-google-app-engine/
It focuses on my current stack, which includes Google Guice. I also use
GWT, but that should mostly be irrelevant.
--
