Re: Interface to a file?

Responding to JMF...

So if I get the idea, the idea is that at the logical/design level the file shouldn't really exist, since it's really just a realization of a persistence mechanism. If anything, there might be an access layer that allows the application to see the persistent data the way it likes, or if I want to get close to the idea of a file, then have a File object with the appropriate access operations as you describe below.

Then if I want to show that there really is a file realizing the persistence, I can do that in a deployment view.

Exactly. And the notion of 'realization' is a nice touch.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
(888)OOA-PATH



.

Relevant Pages

  • Re: Having difficulty refactoring a DB application
    ... SQL is a very specific persistence mechanism and your ... Most OO code does *no* database management. ... addressing) for method calls and local data members. ...
    (comp.object)
  • Re: Database Model - Class, objects and interaction
    ... SQL is not an interface to a persistence mechanism. ... to a data management mechanism. ...
    (comp.object)
  • Persistence management patterns
    ... server side container ... maintaining control over versions (if the software/class changes, ... do not want the persistence mechanism to throw error while retrieving ... What patterns or combinations thereof can I use for a persistence ...
    (comp.object)