Hi Graham,
Graham Chiu wrote:
>
> On Wed, 24 Apr 2002 13:43:20 +0200
> Nenad Rakocevic <[EMAIL PROTECTED]> wrote:
> > google: read soap://api.google.com/GoogleSeach
> >
[...]
>
> This could assume that http is the default transport
> mechanism, and we could supply a refinement for alternatives
>
> eg google/goGetCachedPage/smtp [ .. ]
I would rather make it that way :
service: open soap://api.google.com/GoogleSeach
insert service [use SMTP]
then :
service/locals/goGetCachedPage [...]
..
or maybe :
insert service [get all]
google: copy service
google/goGetCachedPage [...]
..
> and one of the reasons I prefer 'to-soap is that 'read is a
> native, and already overloaded. And if we use a mezzanine
> function, we can proceed regardless of what RT do, whereas
> 'read requires assistance from RT.
Not totally true. 'Read is just a shortcut for open/insert/close.
So, it can be supported when writing a scheme handler (see my work
on MySQL). 'Read is fully polymorphic by definition.
> But, if you really want to use 'read
>
> google: to-soap read soap://api.google.com/GoogleSeach.wsdl
^^^^^^^ ^^^^^^
IMHO, this two additions shoud be useless.
Regards,
-DocKimbel.
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
