Design for single database, multiple applications
Design for single database, multiple applications
- Subject: Design for single database, multiple applications
- From: Mark Wardle <email@hidden>
- Date: Mon, 9 Aug 2010 22:02:22 +0100
Hello.
The time has come for me to sketch out the next version of my patient
record system.
I have several frameworks and one application. The latter is a bit
gnarly (to use a technical term) and unwieldy and I think it would
make sense logically (and from a user interface point of view) to have
separate applications for different specific functionality.
Is there a WebObjects-way of passing sessions between applications or
is it simply a case if using a manually created cookie with an
encrypted username and somehow safely providing a time-limited
credential?
I have enabled different sub-applications as part of the single main
app dynamically based on runtime data - and I'm definitely undecided
whether breaking it up is the right way forward. On the other hand,
factoring out the common stuff and creating a robust core framework
has a certain aesthetic quality to it.
All opinions gratefully received.
Many thanks,
Mark
--
Dr. Mark Wardle
Specialist registrar, Neurology
(Sent from my mobile)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden