Re: Is it a facade
Ed wrote:
> Sanjay skrev:
>
> > Was curious to know if I can *only* call a pattern which gives client
> > an abstraction of the subsystems in a single call, a facade or could
> > it be possible that a ModuleManager class that provides many API's to
> > clients to finally build a Module entity also as Facade.
>
> Remember that we use patterns as communicative short-cut. A Facade is
> the popular term given to a particular solution to a particular
> problem. The GoF book is sufficiently well-read that when you say,
> "Facade," to an OO programmer, he'll probably know that you're talking
> about the Facade from GoF, and therefore know that you're trying to
> encapsulate a subsystem behind a small number of interfaces.
May be I should point out that I am talking about Design Patterns and I
am expecting people to look from an OO programming view.
>
> You can call such subsystem encapsulation anything you like. You can
> call it, "ModuleManager." You can call it, "The ominous, freezing,
> Plutonic wasteland." But programmers won't know what you're talking
> about, and you'll find yourself explaining your design, over-and-over
> again, to audiences that will all give rougly the same response:
ModuleManager is a random name I gave to a class that has few API's
exposed for clients to create an entity. I guess I am talking very
generically since I don't have any module in mind as such.
>
> "Oh, you mean it's a Facade."
Yes, I meant the Facade Design patern which I read few days back :)
>
> .ed
Sanjay
.
Relevant Pages
- Re: Help on choosing a valid pattern: composite or not?
... But that class would only exist in the UI subsystem in my ... In the GUI subsystem where GfxNode might live I am expressing an entirely different set of paradigms for display and I might have a handy MVC infrastructure to make the code simpler, which is where GfxNode comes into the picture. ... I can go directly to the View from the subsystem interface. ... Let's say I have defined a Facade pattern class for the interface called, for lack of anything better, GUIInterface. ...
(comp.object) - Re: Text terminal rendering design
... Which is exactly what would happen in your case when the interface ... Every client would have to ... The only alternative you have is to provide a true Facade ... you have to kludge your implementation of the subsystem. ...
(comp.object) - Re: Classes as units of reuse
... Component ABC { ... The thing that is not clear in your pseudo code is the nature of the relationship between ABC and DEF. ... IMO, the second approach would be the best where one abstracts some set of objects with the proper functionality and then decouples their details from the rest of the application via a Facade interface to which the clients all talk. ... In the OO paradigm one basically has three levels of logical indivisibility: subsystem, object, and responsibility. ...
(comp.object) - Re: Is it a facade
... Creation subsystem would understand a suite of larger data structures ... Unless the site itself very conveniently puts that data in the DB, you need to have the site software give you the information _as it happens_. ... Without some sort to API provided by the site you will just not be able to do much useful in monitoring what is going on interactively. ... So you will need some sort of Facade that is tailored to talk to their particular site API. ...
(comp.object) - Re: Is it a facade
... an abstraction of the subsystems in a single call, a facade or could it be possible that a ModuleManager class that provides many API's to clients to finally build a Module entity also as Facade. ... all of the above, depending on problem context. ... It is not uncommon to hide detailed processing at a lower level of abstraction in another subsystem. ... Your third issue address the problem where each subsystem has unique specialized services that the client may need to access in particular contexts. ...
(comp.object) |
|
