Hi Don,
<< This is not meant to be a hostile criticism of Rugby, just to point out
that there is no magic. >>
Agreed. There is no solution which will work in every situation. I guess I
would say that if you decide some part of your app should make remote calls,
Rugby is up to the task as well as
On 14-Jan-02, Gregg Irwin wrote:
> << But isn't this incredibly slow compared to running the function
> locally?
>>>
>
> Yes, but...it depends on your connection, the overhead of the
> marshalling, and the amount of time spent in the function, as well as
> the frequency of the call.
>
> Even m
Hi Jason,
> LoL :-) that's really wonderful.. thanks for de-mystifying teh subject in
> such an entertaining and lucid way.
Glad you liked it. There's hope for me yet!
> btw do you know Scott McCloud's brilliant cartoon-books: 'Understanding
Never met them. But I'll make a note to check out th
On 13-Jan-02, Jason Cunliffe wrote:
>> Here's an attempt (WARNING long winded). ===Why a request broker?
>> ===The dark times.
>> ===Rugby
>> ===Scenarios
>> Rugby does it's job so well it seems overkill to even talk about
>> Request Brokers.
> Brett
> LoL :-) that's really wonderful.. thanks f
Hi Don,
<< But isn't this incredibly slow compared to running the function locally?
>>
Yes, but...it depends on your connection, the overhead of the marshalling,
and the amount of time spent in the function, as well as the frequency of
the call.
Even making an out-of-process call on the same ma
Hi Rondon,
> I have a few doubts about rugby. I can make a direct call using rexec and
sexec, putting the service at http layer. So I can call a service through
rugby to be sent to a browser, but how can I send back args to my functions
inside rugby server via my IE5?
> What are the variables tha
Don Cox wrote:
>On 13-Jan-02, Brett Handley wrote:
>
>>Say you have a script with some functions defined and the main
>>execution code. Rugby allows you to split that script up to run across
>>more than one Rebol process (usually on different machines). You could
>>put all the functions in one sc
On 13-Jan-02, Brett Handley wrote:
> Say you have a script with some functions defined and the main
> execution code. Rugby allows you to split that script up to run across
> more than one Rebol process (usually on different machines). You could
> put all the functions in one script and place tha
> Here's an attempt (WARNING long winded).
> ===Why a request broker?
> ===The dark times.
> ===Rugby
> ===Scenarios
> Rugby does it's job so well it seems overkill to even talk about Request
> Brokers.
Brett
LoL :-) that's really wonderful.. thanks for de-mystifying teh subject in
such an enter
> I have a few doubts about rugby. I can make a direct call using rexec and
sexec, putting the service at http layer. So I can call a service through
rugby to be sent to a browser, but how can I send back args to my functions
inside rugby server via my IE5?
> What are the variables that I must rea
Hi Brett and Rebolers!
I have a few doubts about rugby. I can make a direct call using rexec and sexec,
putting the service at http layer. So I can call a service through rugby to be sent to
a browser, but how can I send back args to my functions inside rugby server via my IE5?
What are the var
On 13-Jan-02, Brett Handley wrote:
> Hi Jason,
>> Well I know it is one of REBOL's secret weapons of Mass Delirium,
>> but I still don't quite get it. I would welcome a beginner's
>> explanation about request brokers, and expecially anything which
>> expands on the rugby site documentation.
> H
Hi Jason,
> Well I know it is one of REBOL's secret weapons of Mass Delirium, but I
> still don't quite get it. I would welcome a beginner's explanation about
> request brokers, and expecially anything which expands on the rugby site
> documentation.
Here's an attempt (WARNING long winded).
===
13 matches
Mail list logo
