Package: debconf Version: 1.5.40 Severity: wishlist Owner: mo...@debian.org
Hello, as previously noted in #629405 [1], I'm working on a new Debconf::Frontend::Kde frontend which would start and delegate all frontend tasks to the external KDE-native debconf-kde-helper program. Debconf::Frontend::Kde would communicate with debconf-kde-helper process via FIFO pipes and speak Passthrough frontend protocol. While this is still work in progress, I came across an issue. When Debconf::Frontend::Kde setups FIFO pipes and forks debconf-kde-helper process, it has no way of knowing if or when debconf-kde-helper is ready to accept protocol commands. Therefore, I think it makes sense to add an equivalent of the ping command to the debconf (Passthrough) protocol. It could be as simple as: ---> PING <--- 0 pong In this case Debconf::Frontend::Kde could ping debconf-kde-helper immediatelly. As soon as it receives proper "pong" reply from the helper, it could assume that the helper is ready. However, I'm wondering what name of the ping command should be: PING or maybe X_PING? Please note that this command does not have to be a proper debconf protocol command. It may be Passthrough-only and not so widely documented on the same level as DATA command is. What do you think? P.S. When I get confirmation on "ping" command name and implement this new frontend, I will send patches to this bug. I also have an idea how to solve original request of #629405 without throwing all code of the current frontend away. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629405#15 -- Modestas Vainius <mo...@debian.org>
signature.asc
Description: This is a digitally signed message part.
