Hi Beneroth,
Sorry just to reply now, it was a hectic weeks for me.. but thanks for this
explanation! I am also trying to learn PicoLisp as much as possible from these
threads.
I want to promote PicoLisp as much as I can, I am working on something right
now and hopefully I can provide a positive feedback soon, cheers!
BR,Geo
On Wednesday, 4 September 2019, 12:42:06 am GMT+9, <[email protected]>
wrote:
Hi Geo
psh (located in the bin/ dir within picolisp/ dir) is "picolisp shell" (or
process shell?), is a tool to get a REPL to a running picolisp app process.
The implementation is a bit tricky, basically it does a HTTP request to the
running app server (to initiate a session process),
and then that process gets told to bind to a tty, so you get a REPL to the
running application - a child process, same as normal application user
sessions, not the master process.
So with psh you can work on the live application, like just another user.
Very useful for debugging or live patching. If it is really a productive
system, you should be careful with database transactions,
as the database is write-locked for all users until the transaction started
with (dbSync) is finished with (commit 'upd) or canceled with (rollback).
Better use the auto-transaction methods (the ones with the ! in the name) like
(put!>).
Best regards,
beneroth
On 03.09.19 16:30, George Orais wrote:
Hi CK,
Im also currently learning PicoLisp web dev and this thread is indeed
informative.
For your question I think Alex mentioned about psh? Im not so sure but I
think I read somewhere about psh and its usage and this might be the answer.
BR, geo
