Livio,
Hello there!
I have tested today's CVS + DPI bookmarks and things seem very well!
Good! Did you use `convert` or started from scratch? Or wrote a simple script to import from elsewhere? :)
Jorge Arellano Cid writes:
[...]
With respect to staying alive, I also think it should end after closing dillo. Maybe sending a termination request at exit time could work fine, but I need some time to think about it...
One small suggestion is that this termination be dealt with unix signals. I don't see clearly what are the advantages of using sockets for DPI's over pipes (expect running the server and the browser in different machines, but... is that useful?).
Sockets are two-way channels and, BTW, unix domain sockets allow access from the local machine only...
Anyway, since we're using unix domain sockets, I'll assume we are local users only, and I'll also assume that signals are ok.
The advantage of using signals for termination (instead of a "proper" DPI request) is that anyone can "safely" terminate a specific server. If Dillo crashes, or if it is buggy the server may dangle alive. But if you (Dillo or a user) kill with -TERM, we can have the servers set up the termination code inside the -TERM signal handler, and hence free it's resources correctly (unsaved files, opened ftp connections, etc.).
I understand. BTW, bm_srv12 has a SIGTERM handler (just in case the server is killed or brought down with Ctrl-C). The problem is that dillo should keep track of the process ID of each server (and those can be taken down and re-launched without dillo's intervention). As you see, both schemes have some glitches; if you find an easy way to deliver the signals, I'd be all for it. Cheers Jorge.-