The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

jcmorris-mts (4) [Avatar] Offline
#1
Robert et. al.

I like the concept of a portal or dashboard for my current project, but I'm stymied as to whether I should make each component application stand-alone rather that as "views" or "composite panels" in a dashboard-type app.

When is it better to architect a GWT application as a "dashboard type" app with a main app and many helper apps vs. creating a separate app for each helper and exposing them via a single sign-on login?

Any recommendations?
Is there a clean (simple) way to implement single sign-on with multiple GWT apps?

Thanks!
-JM
robert.hanson (173) [Avatar] Offline
#2
Re: Creating a Main App w/ Helper Apps VS. Separate Apps w/ Single Sign-On
I hesitate to recommend something here, it really depends a lot on the specifics of the application and your personal preference.

With a single app, the overall size of the app is reduced (multiple apps would have duplicated code). With a single app there are no single sign-on issues. With multiple apps there is no upper size limit, the app can continue to grow indefinitely.

As for single sign-on, you would probably use the normal cookie based approach, with a session stored on the server. Basically just turn on sessions in your app server (I am assuming a Java server), and store the User object in the session. Any RPC calls would rely on the credentials in the User object, and not based on anything the client sends.