John Dutcher wrote:
> Is a series of Rebol scripts that constitutes a complete application e=
xecutable in the browser plug-in with little or no change. This consi=
sts of scripts which call (do) other scripts in a flow of responses to =
user selections to VIEW displays and revolve around a Rebol file as a d=
atasource.
> =20
Sounds like you should use session-id (and maybe user accounts on the=20
server side) and
simply assume, that the other applets opened after the first log-in=20
belong to the same session, =EFf they come from the same IP (or maybe you=
=20
have a cookie to identify you). Some sort of co-operation is possible,
but means you really can design the overall system well.
The server should create a "session instance", which knows the current=20
state of your overall session.
That way each applet can do its part. You could use semaphores to=20
control the access of several processes to the state and so on.=20
Implement semaphores by the file rename trick.
> Will placing these scripts and the datasource on the server allow them =
to execute via the plug-in pretty much as they would if they were on a lo=
cal drive ?? =20
> =20
About yes. Do first one applet (I like Rebol applets, easier and more=20
lightweight than the most other non-Java alternatives), then somehow=20
learn the session instancing, then do a duo applet and so on. :)
Please don't show the result code to the Rebol purists though, or at=20
least mention that you-did-it-only-because-you-had-to... (And maybe=20
there is another way too!)
--=20
=09
Paavo N.=20
--
To unsubscribe from the list, just send an email to
lists at rebol.com with unsubscribe as the subject.
