Project architecture
Project architecture
- Subject: Project architecture
- From: "Webobjects Developer" <email@hidden>
- Date: Thu, 29 Mar 2007 10:03:44 -0700
I'm a relative newcomer to WebObjects, but I've built a few
applications and feel like I have a good handle on the technology. I'm
thinking about using WebObjects for my next online project.
My question is about project architecture. I envision the following
major components:
- The backend database
- The administrative web site
- The [non-secure] user web site
- The [secure] store web site
My goals are to:
- Hire a non-technical web designer for the user web site and store web site
- Use off the shelf tools like Dreamweaver or Go Live for web design
- Include some dynamic content in user web site
- Provide bookmarkable, non-cryptic links to user web site
For instance, it seems unreasonable for my web designers to deal with
the WO component .html or .wod files of the WO project.
Also, using WO components for the user web site pages makes it harder
to provide bookmarkable links for the pages on the user web site that
have dynamic content.
But if not WO components for the pages, then what?
What are the suggested WebObjects techniques for organizing a project
to meet the goals above?
_______________________________________________
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