[Uim] Reorganization of helper API
TOKUNAGA Hiroyuki
tkng at xem.jp
Sun Aug 7 13:42:23 EEST 2005
On Sun, 7 Aug 2005 18:13:00 +0900
TOKUNAGA Hiroyuki <tkng at xem.jp> wrote:
> On Fri, 05 Aug 2005 19:24:50 +0900
> YamaKen <yamaken at bp.iij4u.or.jp> wrote:
>
> > At Wed, 3 Aug 2005 01:44:00 +0900,
> > tkng at xem.jp wrote:
> > >
> > > Now I'm concidering improvement of helper API of uim.
> > >
> > > At fisrt, now helper API has three problems:
> > >
> > > 1. The word 'helper' is not intuitive.
> >
> > > To solve 1, I propose new name for API, 'message API'. In
> > > addition, this means we don't change helper API, so maybe we can
> > > keep backward compatibility completely.
> >
> > It's a good improvement. I favor both the motivation and the way.
> >
> > > In the new message API, instead of helper-server, message-bus is
> > > used. message bus is a process to relay inter process
> > > communications.
> >
> > I think that -server (or 'd') suffix should be kept to inform
> > users what it is.
> >
> > The suffix implies that it will listen for connections as a
> > background process even if users don't know uim system
> > organization well.
> >
> > For example, how do you feel of uim-mbus-server or uim-mbusd?
>
> I don't prefer short suffix because it's not intuitive. Therefore,
> options are nallowed down to uim-mbus-server and uim-mbus-daemon.
>
> And I don't want to use the word 'server' here, because it's a bit far
> from server according to my definition. i.e. it only transfers
> messages without change.
>
> Consequently, I choose uim-mbus-daemon.
I've forgetten to wrote the mail which have same content. I guess I
became a senile person... orz
Please ignore previous mail.
Regards,
--
TOKUNAGA Hiroyuki
tkng at xem jp
More information about the uim
mailing list