Re: Application structure for NLB
From: J. Baute (QQNVICFBGPKG_at_spammotel.com)
Date: 04/29/04
- Next message: J. Baute: "Re: utf8 encoding problems...please help."
- Previous message: Chris P: "IIS Internal Server Error 500"
- In reply to: Chris Hohmann: "Re: Application structure for NLB"
- Messages sorted by: [ date ] [ thread ]
Date: 29 Apr 2004 00:27:04 -0700
"Chris Hohmann" <nospam@thankyou.com> wrote in message news:<eo#xUiJLEHA.2260@TK2MSFTNGP09.phx.gbl>...
> This is interesting. I was having a discussion recently about this very
> topic. An associate of mine was arguing that we should store images,
> reports and other object within the database to provide "location
> agnostic" access to the files for a web farm scenario. I argued that
> it's seldom appropriate to store object in the database and would rather
> see references to those files stored in the database or simple use a
> virtual directory mapping to provide mirrored access to the same file
> share to each web node. So you can either:
>
> 1. Store the files in the database. Boo!
>
> OR
>
> 2. Use virtual directories to provide mirrored access. Good but not
> great
>
> OR
>
> 3. Use virtual directories in combination with file references stored in
> the database. Great! The best of both worlds.
N°3 sounds like the best solution to me as well, and is basically how
I'm thinking of implementing it. File references are already stored
in the database as partial URL's to a now fixed content directory, but
that can easily be made into a virtual directory without having to
change any hyperlinks in the app itself,
which is nice :)
- Next message: J. Baute: "Re: utf8 encoding problems...please help."
- Previous message: Chris P: "IIS Internal Server Error 500"
- In reply to: Chris Hohmann: "Re: Application structure for NLB"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
