Re: [xml-dev] Exposing resources/services vs hiding implementation details
by Jan Algermissen other posts by this author
Apr 5 2005 9:21AM messages near this date
Re: [xml-dev] Exposing resources/services vs hiding implementation details
|
Re: [xml-dev] Exposing resources/services vs hiding implementation details
& XSLT Michael Champion wrote:
> On Apr 5, 2005 9:16 AM, Bill de hÓra <bill.dehora@[...].com> wrote:
>
>
>
> >If you decide to go the POST route, what you want to avoid are exposing
> >controller URIs (all client requests go to one URI). At least give the
> >things of interest (the equivalent of your objects in your domain model
> >or your table rows in your physical data model) visible identity.
> >
> >
>
> Why " give things of interest (the equivalent of your objects in your
> domain model or your table rows in your physical data model) visible
> identity?"
>
I understand this to mean: create objects (=resources, when speaking
about REST) for the things of interest and expose them to the client
(to make caching of read-data-requests (GET in REST-land) possible.
> That seems to violate the principle of information
> hiding
>
Hmm...making the objects of interest known to the client is not what I
understand by "information hiding". "Information hiding" to me means to
hide the implementation from the client.
Of course there are issues with the granularity of what you choose to
expose (Facade pattern comes to mind[1]), but the extreme of providing a
single poiunt of access (e.g. http://foo.org/myService ) to POST
everything to just doesn't seem to cut it when it comes to scalability
and integratability.
But maybe I misunderstand your point.
Jan
[1] http://c2.com/cgi/wiki?FacadePattern
> that has been around since before OO. It seems to be simply a
> Bad Idea to expose internal details in a world where slimeballs have
> proliferated who would love to subvert your website for fun and/or
> profit. Why not hide them behind a "controller URI" that accepts
> requests and gives them a going over with the polygraph and
> protocoscope, then routes them to whereever the system thinks they
> should be routed at this moment?
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
>
>
--
Jan Algermissen
Consultant & Programmer
http://jalgermissen.com
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>
Thread:
Claude L Bullard
Marc de Graauw
Joe Gregorio
Bill de hÓra
Michael Champion
Uche Ogbuji
Jan Algermissen
Uche Ogbuji
Rich Salz
Jan Algermissen
Rich Salz
Michael Champion
Bill de hÓra
Michael Champion
Uche Ogbuji
Bill de hÓra
Robert Koberg
Peter Hunsberger
Michael Champion
Leigh Dodds
Jan Algermissen
Leigh Dodds
Bill de hÓra
Michael Champion
Leigh Dodds
Michael Champion
Rick Marshall
Bill de hÓra
Robert Koberg
Rich Salz
Leigh Dodds
Rich Salz
Leigh Dodds
Rich Salz
Leigh Dodds
Andrzej Jan Taramina
Rich Salz
Bob Foster
Jan Algermissen
Mark Baker
Michael Champion
Michael Champion
Mark Baker
Mark Baker
Michael Champion
Bill de hÓra
Rich Salz
David Lyon
Rich Salz
Joe Gregorio
Rich Salz
Joe Gregorio
Saptagirisa N
Arvind Singh
Rich Salz
Joe Gregorio
Rich Salz
Joe Gregorio
Rich Salz
Dave Pawson
Mark Baker
Joe Gregorio
Mark Baker
Rich Salz
Michael Champion
Elliotte Rusty Harold
Joe Gregorio
Michael Champion
Jan Algermissen
Bill de hÓra
Joe Gregorio
Charles Woerner
Rich Salz
|