[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Exposing resources/services vs hiding implementationdetail

• To: Michael Champion <michaelc.champion@g...>
• Subject: Re: Exposing resources/services vs hiding implementationdetails
• From: Leigh Dodds <leigh@l...>
• Date: Tue, 05 Apr 2005 23:31:04 +0100
• Cc: xml-dev <xml-dev@l...>
• In-reply-to: <e3a5cb2c050405094871a224e6@m...>
• References: <200504051139.j35BdXDR050954@s...> <42528FB5.7040300@p...> <e3a5cb2c0504050804887b795@m...> <4252B522.70600@p...> <e3a5cb2c050405094871a224e6@m...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Michael Champion wrote:
> ...I would have to agree that
> security by obscurity is not something to rely on, but I'm not sure I
> would agree that advertising your internal architecture to potential
> hackers is a great idea either.

As hackers have just as much focus mucking about with plain ole web
sites, isn't that an argument for hiding your entire site behind
"http://www.example.com/crypticAddress" also?

I don't see how defining a public URL space exposes any details about
my application structure. I've done it, for both human and machine
oriented interfaces, and you can't tell from the url structure or
response formats what my backend is doing. Or even if the entities in
the URI map 1:1 with entities in my database schema.

Cheers,

L.

• Follow-Ups:
  • Re: Exposing resources/services vs hiding implementation details
    • From: Michael Champion <michaelc.champion@g...>

• References:
  • RE: What Does SOAP/WS Do that A REST System Can't?
    • From: "Marc de Graauw" <marc@m...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Bill de hÓra <bill.dehora@p...>
  • Exposing resources/services vs hiding implementation details
    • From: Michael Champion <michaelc.champion@g...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Bill de hÓra <bill.dehora@p...>
  • Re: Exposing resources/services vs hiding implementation details
    • From: Michael Champion <michaelc.champion@g...>

• Prev by Date: Re: Exposing resources/services vs hiding implementationdetails
• Next by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• Previous by thread: Re: Exposing resources/services vs hiding implementation details
• Next by thread: Re: Exposing resources/services vs hiding implementation details
• Index(es):
  • Date
  • Thread