"interesting idea ... " Through the http server you can call any PL function, in that function you (load) stuff before doing what you need to do.
>From the above it kind of follows that I use a single bootstrap/entry/routing function, so I only need to do the loads there and nowhere else. On Wed, Jul 17, 2013 at 5:23 PM, Thorsten Jolitz <tjol...@gmail.com> wrote: > Henrik Sarvell <hsarv...@gmail.com> > writes: > > Hi Henrik, > > > When developing web apps I keep the code for the server and the rest > > separate and reload the rest on every request. No need for restarts at > > all that way. > > interesting idea, not sure how you actually do that, but would make > things smoother in the not so rare case of reaching a 'bad' state during > development. > > > Unless you're actually fiddling with the actual server code, then it > > can't be helped I suppose... > > I don't, so that would not be a problem. > > > On Wed, Jul 17, 2013 at 3:33 PM, Thorsten Jolitz > > <tjol...@gmail.com> wrote: > > > > > > Rowan Thorpe <ro...@rowanthorpe.com> > > writes: > > > > >> On Wed, 17 Jul 2013 09:22:14 +0200 > > >> Thorsten Jolitz <tjol...@gmail.com> wrote: > > >> > > >> ..[snip].. I ran into this problem when experimenting with the > > >> web-framework and my app got into a bad state. When restarting > > >> then, PicoLisp tells me something like 'Port is already used', > > >> so I tried to kill the still running (*) PicoLisp processes > > >> with a simple 'kill PID', but to no avail. > > >> > > >> [* are they still running? 'ps' shows them with a '?', and I > > >> shutted them down on the command-line, so they shouldn't. But > > >> somehow they still block the port, and the more I shut down, > > >> the more are shown by 'ps'] ..[snip].. > > > > > > Sorry for asking the obvious question, but have you waited the > > > couple of minutes needed for the kernel (depending on which > > > kernel) to eventually clean orphaned ports itself? It *may* > > > actually just be the port remaining open because the owning > > > process didn't cleanly shut it?: as mentioned here > > > http://superuser.com/a/127865 > > > > > > Not obvious for me, obviously, but definitely the right question - > > no I did not wait, and I did not know I have to wait a couple of > > minutes. > > > > So thats probably the root of the problem, unrelated to PicoLisp. > > Though a bit of a hassle, since it takes away the huge advantage > > of PicoLisp's millisecond start-up time somehow, and shutting down > > a PicoLisp process and restart is not a prime option anymore if a > > couple of minutes waiting are involved. > > > > Thanks for the interesting link! > > > > > > > > -- > > cheers, > > Thorsten > > > > -- > > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > > > > > > > > -- > cheers, > Thorsten > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
