Where Does File System Singleton Go?
- From: "Cody Powell" <cody@xxxxxxxxxxxxxx>
- Date: 23 Sep 2005 09:28:51 -0700
Greetings all,
We currently have designed a singleton class that will handle all the
user's interaction with the local or network file system. Reading a
file, writing out to a file, etc will all be handled by this one
object. The design was simple enough; a debate surfaced, however, in
where to place this object within the system architecture.
Currently, the application contains 3 tiers: presentation, business
logic, and data access (used in a client-server manner). Many of the
files we'll be loading from the file system will be indistinguishable
from data retrieved from a table in the database, although that doesn't
hold true for all files.
Based on this set-up and your past experiences, in what tier do you
think this FileSystem object should be placed? We're not even close to
a consensus on this issue right now, so if anyone has any idea of the
best practice when it comes to this specific architecture issue, I'd
love to hear it. Thanks,
Cody Powell
.
- Follow-Ups:
- Re: Where Does File System Singleton Go?
- From: iamfractal
- Re: Where Does File System Singleton Go?
- Prev by Date: Re: Modeling
- Next by Date: UML Modeling Tool like Enterprise Architect
- Previous by thread: Tool for reverse engineering C++ code
- Next by thread: Re: Where Does File System Singleton Go?
- Index(es):
Relevant Pages
|
