support mutiple instances about remi

[dddomodossola]

Yes, in case of different applications you can change the port by the configuration.py file. But maybe we can enable the library on finding automatically the best port number.

[nzjrs]

yes I know I can change it, but what if I want to launch the same app with the same source code twice?

you can do something like this to get a random free port

server = TCPServer(('127.0.0.1', 0), Handler)
host, port = server.socket.getsockname()[:2]
print "we are on port", port

[dddomodossola]

Fine, I will do this soon. ;-)

[KenT2]

If you are going to do this please make it optional. I intend to autostart the server when the Pi is powered up and a terminal window will not be open to see the port number that is printed.

The solution could be that if the port is left blank in configuration.py then a port is automatically selected. Presumably something will need to be done for the websocket port as well.

[nzjrs]

The websocket port is an implementation detail. it should always be an ephemeral port

IMO, the default behaviour should be to just work - i.e. both ports should be ephemeral and random. Hardcoded ports should be optional unless you are targeting the framework to be used by only one app at a time...

[cyberpro4]

A great solution could be listen on default port (from code / configuration file) and, when already used, switch to random port

[nzjrs]

I'm working on this, and cleaning up the whole configuration system, in https://github.com/nzjrs/gui/tree/multiple-instance

[dddomodossola]

Ok John, but take care about the parameter MULTIPLE_INSTANCE in configuration.py file. This parameter changes the behavior of the server in case of multiple clients to the same App. If True, multiple instances of App class are created. If False instead, all the clients shares the same App class instance.

[nzjrs]

Thanks, it was a bit confusing!

What would be a reason to run MULTIPLE_INSTANCE=True? I can't think of a use at the moment

[dddomodossola]

Image a collaborative App, multiple user can interact on the same interface.. I do not have a specific use case now.

[cyberpro4]

A simple address book application, with a name/surname filter: when someone change the filter, this one shouldn't be shared with other clients.

[nzjrs]

A simple address book application, with a name/surname filter: when someone change the filter, this
one shouldn't be shared with other clients.

how is the author of such an app expected to know which client they are talking to, and should they care? is it expected that you poke around in self.client_address from main? are all apps otherwise destined to be stateless?

I get the intention, but I wonder if the current implementation has been well considered.