You piqued my interest in what you were doing. What is your new scheme?

Brett.

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 24, 2000 9:29 AM
Subject: [REBOL] need client/server communication mechanism... Re:


> sorry. Have no idea where my mind was when I was writing this. Solved all
issues without server-side
> rebol assistance...
>
> Rishi
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, September 23, 2000 11:03 AM
> Subject: [REBOL] need client/server communication mechanism...
>
>
> > Hi. I'm planning to make a suite of utilities in R/view for my own
personal use. What I want to do
> > is:
> >
> > - insert log-in.r file in my webserver that runs in client and asks for
my user name/password
> > - after entering log-in info, log-in.r needs to communicate with another
.r file on the server.
> Sort
> > of like cgi. (don't know how to do this...)
> > - Once password is checked, a .r file will be outputed and run on client
machine. It will contain
> a
> > bunch of my .r graphical apps I can click on.
> > - These apps should have ability to communicate with a server-side .r
file, meaning it has to run
> on
> > the server like cgi. The reason for this is because I plan to save all
my data on the server.
> > Basically, I plan to use the server as my diskette.
> >
> > This is kind of similar to the way html works with cgi or servlets...
Rebol can currently download
> > scripts from the server and run them locally. It can also run remotely
in the form of cgi scripts
> > for html...But I don't think there is currently a way to execute rebol
scripts remotely by calling
> > it from a client side rebol script.
> >
> > I hope this is clear description... Help would be appreciated. If I can
get this to work...I can:
> > - use any computer in the lab to access my programs
> > - use any server as my network operating system/diskette.
> > - use rebol/view browser as my file manager.
> >
> > Thanks.
> >
> > Rishi O.
> >
>

Reply via email to