World: r3wp

It might be that a single computer should be opened instead of opening 
the whole room

hum... and the proxy configuration is handled by small cgi requests?

Are you thinking about security risks?

I compress the CGI request so it's not readable

I POST compressed data

you see, what I see here is that the actuall application data is 
on the server and your browser based plugins are just synchronised 
to it.

so using cgi for that kind of think (for liquid) is almost impossible, 
cause the viewers need to get the information BACK.

if someone else changes my setup, I have to be able to receive it.

so in reality, each time a computer opens up a view of the current 
state of each thing, it should have its own listener port.

When the gui starts I show servers state. As soon as a teacher clicks 
a button for a room he is changing the state...

but now you add the concept that "another" computer changes your 
state... you have to be made aware of that change.

so unless you can listen to someone, you will never know.

I see...

liquid can help you automate the process easily, but you still need 
to allow each thing, to be aware of itself.

or rather, of the other things it relates to.

Can I poll a status update from the server each, let's say, 2 mins?

The poll results should generate a data flow...

yes

actually, internally that is how liquid functions, it asks for state 
of dependencies.

this is the purpose of the  instigate function.

I am at the point of making my liquid net module for liquid, which 
would alleviate the need for a cgi-based system in your setup.

I am wondering what to do: on one hand I'd really like to create 
a liquid application, on the other hand I must finish the program 
in a few days...

but its nowhere near ready... I'm starting to look at the discrepancies 
of tcp/ip and liquid models.

hehe, right now... with the cgi in between, I don't think you'll 
get a lot more out of building it in liquid...

haw should the net module work? ?services?

if elixir where ready for release, then, yes it would be a simple 
click and drag... but alas, its not there yet..

it will be direct tcp intercommunication in between nodes.

using encryption if you have those options in your license.

I will try to use the liquid concepts adding attributes to the nodes 
and do a "classical" plugin for the proxy

it should be possible to add an adaptor in order to plug a liquid 
system within a reb service, but thats a later stage.

if I had just a bit more time, I'd be glad to help, but comming back 
from the devcon has but a strain on my time (a lot of time to make 
up at work and at home)

plus I am working on getting a quick Revault demo site ASAP.

Nevr mind, Maxim. Talking about this with you suggested me easier 
way to implement such services and this is an help too!

no problem, I'm happy to help.

During the devCon I "saw" some GUI while you were presenting your 
programs, are those scripts available to the public?

but seeing people's real use cases helps me see where to put the 
time on whatever I do next, and your example shows me that I am dead 
on my priorities  :-)

elixir no, in two weeks  (beg june)

glayout yes.

liquidGL next week.

liquid is online.

all on rebol.org

I am really curios as I cannot come to Paris... Last DevCon was in 
my school so it was simpler to me to attend ;)

I tried your examples on the site

cool, happy to know that people are starting to try out liquid.

I will be giving a lot more tutorials and examples, in the following 
weeks.

I am at a point where all my stuff basically works, I just need to 
start disseminating the information, spreading the word.

and supporting people who use it.

A suggestion: put the working full script as a downloadable file 
(rebol.org or a link from liquid site) at the beginning of the page. 
I did the example step by step following the page and, at the endo 
of my tests I found the full script I colud copy and paste!!!

and it seems, by a strange twist of faith, that I suddenly have A 
LOT more time on my hands... (I'll let you figure out why ;-)

thanks, good idea  :-)  point taken