Re: Advice on Project Approach - Single or Multiple Apps?
Re: Advice on Project Approach - Single or Multiple Apps?
- Subject: Re: Advice on Project Approach - Single or Multiple Apps?
- From: Arturo Pérez <email@hidden>
- Date: Tue, 3 Feb 2004 10:09:18 -0500
On Feb 2, 2004, at 12:11 PM, Kieran Kelleher wrote:
1) Build the whole thing as one complete single WebObjects application
myself getting page elements and graphic bits and pieces from graphic
design as required when constructing my WO HTML components, OR
2) Have graphic design build basic static HTML site for the "public"
portion with sales blurb and provide a number of separate WO
applications (all using the same EOModel/EOClasses framework) that are
accessible via URLS from the main static site.
Thinking out loud, option 1 will have advantage of one login, one
session as a user navigates the site, particularly the private
"customer-tailored" and customer accounts portion, so I don't have to
worry about re-authenticating as the user moves from app to app.
Having been there, done that :-)
I would go with option 2. The re-authentication issue can be handled
easily by placing a cookie within
the domain. If you're not allowed to use cookies then I would do
option 1.
----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.