Andrew S. Townley wrote:
> On Mon, 2006-07-17 at 14:09, Harm Smit wrote:
>>Absolutely. The lightbulb10.turnOn() formulation was merely given to
>>set it off against lightbulb10.PUT(<state="on"/>) or something
>>similar.
>>In actual practice, the lightbulb and its services would be discovered
>>dynamically.
>
> Ah. What threw me was the 'lightbulb10' part rather than turnOn vs.
> PUT. I'm not sure that I would've characterized the REST approach via
> the mechanism you did, but I get your point.
I also think that it's important to note that lightbulb10 is really a virtual
name in this example, not a written name in the software. It's a reference to
an instance.
I see some comments like Andrew's that make it seem that many may not always
think about how software can use discovery techniques to arrive at an instance
of a service rather than having hard coded knowledge.
for( Light l : getLights() ) {
l.turnOn();
}
getLights() is the discovery piece. It might hardcode the instances, it might
use Jini lookup, UDDI, a CORBA ORB etc. The enumeration of the choices and how
that is abstracted is part of the software system design.
Gregg Wonderly
------------------------ Yahoo! Groups Sponsor --------------------~-->
Something is new at Yahoo! Groups. Check out the enhanced email design.
http://us.click.yahoo.com/SISQkA/gOaOAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
