Hello there! I have tested today's CVS + DPI bookmarks and things seem very well! 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?). 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.). If, on the other hand, there is an interest in making server and browser work on separate machines, then I would suggest to besides normal DPI termination methods, the signal termination handler still be used, as to always let the user clean things up when needed. just my 0.02 reais (which won't buy anything these days :-((( -- Livio <livio@ime.usp.br>