Closed GoogleCodeExporter closed 9 years ago
I've just run multiple instances of phpdesktop and seems that
there is no problem running multiple php web-servers on the
same port. Why is that possible?
Original comment by czarek.t...@gmail.com
on 13 Jan 2013 at 5:22
Mongoose seems to be fine when running multiple instances of an
application with each instance starting web-server on the same port.
Original comment by czarek.t...@gmail.com
on 19 Jan 2013 at 6:04
[deleted comment]
See this topic on mongoose-users forum:
"How to check if port is free?"
https://groups.google.com/d/topic/mongoose-users/vBJ0bZHmOv8/discussion
Original comment by czarek.t...@gmail.com
on 2 Feb 2013 at 3:28
[deleted comment]
Check also if "remote-debugging-port" is free. If not, generate some random
port for that too.
Original comment by czarek.t...@gmail.com
on 24 Jan 2014 at 5:10
When launching a second application that has the same listening port set, then
the content from the first application that started a webserver on that port,
will be served. So this is some serious issue. If there are two different
applications and we display application 1 content in application 2, then this
is really bad.
Original comment by czarek.t...@gmail.com
on 25 Jan 2014 at 10:08
[deleted comment]
Each instance of the same application should run on a different port, otherwise
the --cgi-environment argument used to launch a second application instance,
will not take effect as it is the first webserver that will be serving content.
Original comment by czarek.t...@gmail.com
on 25 Jan 2014 at 10:19
After a minor modification to mongoose sources, it now accepts port "0",
thereby OS assigns a random free port. Now I need a way to get know the port
that was assigned. Created a topic about that on mongoose-users group:
https://groups.google.com/d/topic/mongoose-users/spyD60wLcGE/discussion
Original comment by czarek.t...@gmail.com
on 25 Jan 2014 at 1:04
Fixed in revision 8091beb8d108. When port is set to 0 in settings.json, OS will
assign a random free port.
Original comment by czarek.t...@gmail.com
on 25 Jan 2014 at 3:44
Chrome 31.4 and MSIE 1.12 released.
Original comment by czarek.t...@gmail.com
on 26 Jan 2014 at 1:25
Original issue reported on code.google.com by
czarek.t...@gmail.com
on 13 Jan 2013 at 5:13