I assume you fear that a port gets binded to a socket twice. That can not happen, since unix/linux does not allow two processes to bind the same process. (app) calls the pil function (port). The port function itself is able to find a unused port an binds it. For more details read (doc 'port) If you are good with C you might want to look inside net.c and understand doport. Picolisp takes care of the ports for you.
2015-11-21 9:36 GMT+01:00 Denis Fourt <denis.p...@hotmail.com>: > Yes, this helps, I did not understand that psh was a debugging tool. About > (app), I still would like to know, if there was a way to run more than one > application on the same computer and be sure that they would not by > accident decide to use the same port. I understand that within one app > there is no problem (as long as there are not too many users), but with two > or more? Or do my network programming memories need a refresh? > > Denis > ________________________________ > > From: johtob...@gmail.com > > To: picolisp@software-lab.de > > Subject: Re: questions about the gui > > Date: Sat, 21 Nov 2015 08:51:43 +0100 > > > > > > Hello, > > > > It is a local shell that connects to a local webserver. > > It can be used for webdevelopment, you can expect variables and so on. > > (app) open a new process with a new port. So each process and each > > single user linked to it can has a own state. The user can connects to > > his new port > > Does it help? > > > > Am 21.11.2015 08:28 schrieb "Denis Fourt" > > <denis.p...@hotmail.com<mailto:denis.p...@hotmail.com>>: > > Hello, > > After reading the gui documentation, I would like some help on the > > following topics, please : > > a) I am not sure to understand the purpose and the uses of the psh > function > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe >
