[openi18n-im:01249] private iiimd and single iiimd
AShiZaWa KaZuNoRi <[email protected]>
| Newsgroups | gmane.comp.internationalization.input-methods |
|---|---|
| Message-ID | <[email protected]> |
All, Date: Wed, 02 Mar 2005 00:30:05 +1000 From: Leon Ho <[email protected]>: > > Features that are locked for r12.2 with owners: > ----------------------------------------------- ... > - Single iiim server for clients on single X desktop [kasha] > - Enhance iiim server on private user mode [kasha] Brief description how the implementation will be. Please give your comments if you have any issues. ---- default path to UNIX domain socket (port) for private iiimd: /tmp/.iiim.${USER}/${DISPLAY_NUMBER} The mode of /tmp/.iiim.${USER}/ will be 0700. mkdir("/tmp/.iiim.${USER}/", (S_IREAD | S_IWRITE | S_IEXEC)); chmod("/tmp/.iiim.${USER}/", (S_IREAD | S_IWRITE | S_IEXEC)); iiimx: create an atom IIIM_IIIMD_PORT and associate it to a port if iiimd is private then start iiimd with the port endif create an atom IIIM_IIIMD_NODE and associate it to a node name open an connection to iiimd if data comes from iiim*cf then relay to iiimd endif iiim*cf: get a node name which is associated with IIIM_IIIMD_NODE if the node name equals to the local node name then get a port name which associated with IIIM_IIIMD_PORT open an connection to iiimd else open an connection to iiimx endif Points: private iiimd: - iiimx starts iiimd automatically when necessary - user can start iiimd manually - iiimd can be started without creating user specific configuration files - namespace based file I/O is mandatory single iiimd for clients on single X desktop - Use X atoms to know how iiimd can be accessed - iiimx acts as a proxy for remote clients - iiimx communicates with remote clients using X protocol - iiimx should have a switch to disable proxy ---- Regards, -- kasha