Lists Home |
Date Index |
On Tue, 2005-04-05 at 11:04 -0400, Michael Champion wrote:
> On Apr 5, 2005 9:16 AM, Bill de hÓra <firstname.lastname@example.org> 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?" That seems to violate the principle of information
> hiding that has been around since before OO.
No it doesn't. I think you misunderstand those old concepts.
> 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
This is a matter for security, not obscurity. If you trust too deeply
in the latter, you lose the former. The key to securing the house is
not to wall over all doors and windows, but rather to put in locks and
give the right people keys.
Again I think you're confusing the issues.
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
Writing and Reading XML with XIST - http://www.xml.com/pub/a/2005/03/16/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286
State of the art in XML modeling - http://www.ibm.com/developerworks/xml/library/x-think30.html