[ALLY] REBOL Modules Doc Re:(6)
From: petr:krenzelok:trz:cz at: 5-Aug-2000 8:18
> Hi Petr,
> In response to my example:
> >> cell-phone: make module! [
> >> title: "cell phone module"
> >> url: http://www.rebol.com:6130/chat-server-module/
> >> ][
> >> signup "me" "rebol-room"
> >> chat
> >> ]
> >> Looks quite useful to me!
> you wrote:
> Since REBOL does not find the words arg-block and body-block defined in the
> module local-module, and since local-module includes the url
> rebol://rebol.TechScribe.com, his local REBOL interpreter will connect to
> the remote REBOL interpreter located on TechScribe.com, at a specific port
> address that is defined by the rebol:// protocol, and bind local-function
> to a function that is created in the local REBOL instance, by using the
> blocks on the remote machine for the function's prototype.
just one comment. Make 'url field more general. We currently have 'Needs field,
which can contain block of needed components, so:
If creating script=module, we could use even 'Needs, e.g. Needs: [Core 2.2 View
1.0 ODBC 1.0 rebol://www.rebol.com/module http://www.rebol.com/some-script.com]
or just what if your module needs to be linked into two another modules? Then
your 'url field should accept also block of urls ....
Do you disagree? :-))
> >In any case, it would require REBOL to have some kind of default protocol
> >RPC, as not all types of schemes are suitable for such kind of behavior.
> Perhaps an implementation of XML-RPC would be sufficient? We really should
> be able to implement that right now.
IIRC someone mentioned it already, but any results so far probably ...