Perhaps it would be better not to muddy the clean syntax of Smalltalk 
unless it cannot be avoided.  Unless a compelling case can be made, 
remote references should be string (and/or symbol) literals, like so:

Object fromURLString: 'http://faraway.machine/getObj/path.to.object'

 or

'http://faraway.machine/getObj/path.to.object' objectFromURL

-Carl

>what would people think of implementing dotted-paths as relative URLs
>(relative to the current img) ?
>
>viewing them that way will save time/effort/brain-cells when we are 
going
>to start sending msgs from one img to another (which sounds like a 
natural
>thing for squeak to allow, and a sure request as squeak matures), not 
to
>mention the usual side-benefits of adopting/re-using standards. the
>'remote' ref would simply be
>
>someSpeedyLocalProtocol://other.img/globally/accessibe/object
>
>(one benefit of using this standard is that with almost no effort this 
can
>then unified with distant-object reaching, through a hook into pws:
>http://the.faraway.machine:8080/getObj/path.to.object)
>
>the url-way also avoids introducing yet-another-concept into squeak,
>keeping squeak more understandable/elegant while it is made more 
powerful.
>
>
>

Get Your Private, Free Email at http://www.hotmail.com