Rugby integration (was) Re: Re: ANN: Rugby configurable (with compre
[1/2] from: koopmans::itr::ing::nl at: 20-Feb-2002 12:46
On Wednesday 20 February 2002 09:56, you wrote:
> > > Now the question/brainstorming:
> > >
<<quoted lines omitted: 22>>
> loop, and run Rugby server in main-server? What would be needed? Simply to
> teach external environments Rugby protocol. So now few questions -
You are right. But RUgby was Inter-REBOL to now.
> - would it be possible to adapt Rugby the plug-in way (or just separate
> versions), that would use tcp, http, xml-rpc, soap (in future for those who
<<quoted lines omitted: 3>>
> HTTP class implementation. The same will probably go for Delphi, VB etc.
> IDEs.
On your OTOH: Yes. The plugins are actually the handlers on top of hipe.
Consider Rugby itself a plugin. RebXR SE is just another.
> - let's suppose we use current HTTP transport mechanism. Is it possible to
> have Rugby protocol a little bit more abstracted? I mean - currently -
<<quoted lines omitted: 3>>
> know how to reproduce in external language. And I am not better even
> mentioning secured connection :-)
I could see if I can make the checksumming optional in the config dialect.
The [*** and ***] are in the post variable, which is a string, as begin and
end-point markers. That should be no problem.
OTOH, I may develop the Rugby bridge on top of hipe. Just a different handler
ready to rock with the rest of the world. What would such a protocol look
like (I ask you as you live in the world that needs it). Surely HTTP based,
but then?
> cmd-string: rejoin [ {rugby-rq: [***} cmd-block {***] xtra-info:
> "1234567891011121314} ]
>
> So, to sum it up - it would be nice to have external app to talk Rugby
> language directly, as that way you can run main-server (your proxy/bridge)
> directly in Rugby server mode.
>
> What do you think about it?
>
I agree. And then marshaling libs in java, perl and whatever. Rebol rules ;-)
> -pekr-
--Maarten
[2/2] from: petr:krenzelok:trz:cz at: 20-Feb-2002 15:14
> > What about not reinventing the wheel and implementing my own listening
> > loop, and run Rugby server in main-server? What would be needed? Simply to
> > teach external environments Rugby protocol. So now few questions -
> >
>
> You are right. But RUgby was Inter-REBOL to now.
>
Of course, I know that ....
> > - would it be possible to adapt Rugby the plug-in way (or just separate
> > versions), that would use tcp, http, xml-rpc, soap (in future for those who
<<quoted lines omitted: 6>>
> On your OTOH: Yes. The plugins are actually the handlers on top of hipe.
> Consider Rugby itself a plugin. RebXR SE is just another.
Eh, so what acutally RebXR is? I thought that Rugby lives on top of Hipe server,
and that http layer is just plug-in to Rugby, and can be exchanged using XML-RPC
for e.g., or SOAP, or custom one. But OTOH, actually - there is only one
transport mechanism in reality - TCP layer - even HTTP lives on top of it. So,
how to make it cleverly configurable? Because if we would like to implement
custom Rugby protocol, we would probably have to change whole Rugby layer?
> > - let's suppose we use current HTTP transport mechanism. Is it possible to
> > have Rugby protocol a little bit more abstracted? I mean - currently -
<<quoted lines omitted: 11>>
> like (I ask you as you live in the world that needs it). Surely HTTP based,
> but then?
Well, the problem is I want it :-) If I really need it is another thing :-) I
want to do some tests. Let's say the main task would be to accept query from some
apps and send them to database engine. The easiest protocol is
http://server:9005?query-string - simply a GET method, containing e.g.
command=exposed-rugby-func,par1=value .....
But currently, I have simply chaos in Regards to what and how should be
implemented to have it the most clean way in regards to Rugby architecture. The
only thing I know for sure is - if external app programmers can't simply create
Rugby message structure, then no easy communication is possible :-)
> I agree. And then marshaling libs in java, perl and whatever. Rebol rules ;-)
>
Yes, Rebol rules! :-)
-pekr-
--
To unsubscribe from this list, please send an email to
[rebol-request--rebol--com] with
unsubscribe" in the
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted