This was my point, many times people 'assume' they are individual apps when they are not. I just wanted to highlight that this should be investigated before the assumption was made.
For example, I just completed an intranet project where it was 'assumed' that there were 3 different systems. WebHelpDesk, FileMaker Pro and the Wicket based portal. Truly, 3 disparate systems and technology platforms. Everyone assumed this but it turns out that WHD can run on top of mysql and FMP can access mysql via ODBC and Wicket, well, its wicket. Result of challenging this assumption is that this client has a single-sign-on across all apps for their users with shared account, user and support ticket info. So I was just challenging the assumption. I think its healthy. John- On Thu, Sep 10, 2009 at 11:52 AM, Martin Makundi <martin.maku...@koodaripalvelut.com> wrote: >> Databases have this cool feature called 'access control' ;) Its fairly >> trivial to set up the db to take connections from both apps and share >> the live data. > > Yes but if we assume that the applications are separate, i.e., they > cannot be merged. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
