I'm going for a client/server architecture....
After the tests I've made yesterday and today is quite obvious that it will be much more easier to make the application this way as I'll have a part that will always be running and, thus, able to retain state much more easily.
And it will also be much more scalable as the pair of named pipes will be on the session data directory.
There will be a general pair of pipes for the command setup and synchronization but, for each session there will be a private set of pipes since the session ID is always known to each session and browser....
So, let's go for implementation...
