Re: App organization

Mon, 24 Jul 2006 09:40:13 -0700

I have read that some folks make the admin pages a separate application, but in this case that seems like overkill;  the main site will contain 3 or 4 pages.   On the other hand I would like to use Apache to password protect the admin area, so I don't have to implement user logins in my first app, and that means I do need something in the URL to hang that off of.

First of all, you should really change your thinking about WebObjects.  You are not building a web site, rather you are building an application that happens to present itself as HTML (among others) to the user.  If you want security in your application you add security to your application.  There are many good books, and some nice examples on how to do this.  I would recommend taking a look at Chuck Hill's "Practical WebObjects" to get an idea of what I'm talking about here.  You will not be using Apache to secure your application's components.

When you build a WebObjects application, the development tools, and build structure is designed to run in a very secure environment protecting your server-side code from the general public.  It does so by placing it in non-public folders on your application servers using a process called a "split-install."  The only resources that  will ever be made public are those that must be delivered by Apache (i.e. images, movies, flash content, etc.).

As far as organizing your WebObjects projects there are many different approaches to that, and I've used several different styles myself over the years.  For this I would recommend reading through the Xcode user manual for options on organizing your projects.

On Jul 23, 2006, at 3:17 PM, [EMAIL PROTECTED] wrote:

In my day job I build websites the old fashioned way, using scripting languages, and I would organize the site I'm building something like this:

User pages are generally at the root of the site, so we might have

/ - home page
/panels - list of all panels of license plates (these are pictures of the panels in the museum)
/panel-detail - info about a selected panel

Admin pages are in their own directory (which shows up in the URL)

/admin - list of available tasks
/admin/add - add a new panel

And so on.

I know that it is standard practice to use Apache Rewrite Rules to make pretty URLs, and I presume I could probably get my site to work this way if I wanted to, but I have a hunch that this is not the WO Way.

I have read that some folks make the admin pages a separate application, but in this case that seems like overkill;  the main site will contain 3 or 4 pages.   On the other hand I would like to use Apache to password protect the admin area, so I don't have to implement user logins in my first app, and that means I do need something in the URL to hang that off of.

So... what would be the proper WO Way to approach this?

thanks,

janine

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:

This email sent to [EMAIL PROTECTED]

--
Robert Walker


 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to