• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Best option for static file access?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best option for static file access?


  • Subject: Re: Best option for static file access?
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 22 Oct 2004 11:50:41 -0700

Hi,


On Oct 21, 2004, at 6:13 PM, Darich Runyan/OMNI INFOSEC LTD HQ wrote:
The client has an ERP system that outputs invoices and quotes for each
individual client in PDF and JPG format. The webmaster then goes and
creates a static webpage for the user that has an image of the invoice or
quote (for quick and easy viewing) as well as links to the PDF files for
them to download. All of these PDF and image files are located within
.htaccess protected directories for each client. In and effort to get them
online with this dynamic system quickly I want to first add in the
authentication page and then just dynamically generate the static pages that
the webmaster is currently doing by hand.

Why dynamically generate static pages? Why not dynamically generate, er, dynamic pages?


This will require access to the
static PDF and JPG files. The question I have is what do some of you more
knowledgeable WO gurus suggest is the best way to access those static files?
Should I continue to maintain them in the webserver/client/root directory
under the .htaccess and have the WO app just access them directly

Probably not. It depends on whether security or throughput is your higher concern. They can be served more efficiently directly from the doc root. However, security is depends on manual htaccess config.


or should
I have them moved to another location outside of the webserver/client/root
to some un-served directory on the server and have the WO app access them
there?
The app would serve them from there. This is slightly less efficient by allows for a more robust and flexible security system.


We are moving the authentication to LDAP in preparations for the
second phase of the app so the .htaccess would really only be to keep casual
surfers out.


In a bit of shameless self promotion :-) may I suggest that you buy the book in my sig. It will save you far more hours in doing the tasks you have ahead than the cost of the book. I find that I use it myself and I wrote (much of) it!

Chuck


--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects




_______________________________________________
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


References: 
 >Best option for static file access? (From: Darich Runyan/OMNI INFOSEC LTD HQ <email@hidden>)

  • Prev by Date: NSData Constructor
  • Next by Date: Re: Reusable components
  • Previous by thread: Re: Reusable components
  • Next by thread: Re: What database
  • Index(es):
    • Date
    • Thread