[openi18n-im:01311] Re: private iiimd and single iiimd

All,

Date: Fri, 04 Mar 2005 15:16:07 +0900
From: AShiZaWa KaZuNoRi <[email protected]>:
> 
> Date: Wed, 02 Mar 2005 00:30:05 +1000
> From: Leon Ho <[email protected]>:
> > 
> > Features that are locked for r12.2 with owners:
> > -----------------------------------------------
> ...
> > - Enhance iiim server on private user mode [kasha]

I've committed related changes to trunk.

This feature is enabled when iiimx is invoked with -iiimd
option.  Without this option, everything should behave the same
as before.

If you start iiimx with -iiimd option, iiimx starts iiimd with
-udsfile option to specify UNIX domain socket file (udsf) name
that will be used for IIIMP communications.  The udsf is also
propagated to X clients via IIIM_SERVER X property.  iiimxcf and
iiimgcf now lookup this property.

You may notice that ATOK for Linux does not work well with this
feature.  But it does not indicate any bug in ATOK for Linux nor
in IIIMF.  It is just because current ATOK for Linux requires
root privilege to be fully functional.

When namespace-based file I/O feature is properly implemented
and all LEs use the API, this private iiimd feature will be
really useful I assume.

Regards,
-- 
kasha