[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kuiserver future (to gui or not to gui)
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2007-02-22 21:50:11
Message-ID: 200702221450.11898.aseigo () kde ! org
[Download RAW message or body]


On February 22, 2007, Thiago Macieira wrote:
> Aaron J. Seigo wrote:
> >if the jobID contained the appServiceName, e.g.
> > appServiceName::NumericalID, we could use that to figure out what the
> > app we should call is. or we could just send the appServiceName with
> > every method in addition to the job id. either way, to guarantee
> > consistency we need the appServiceName.
>
> Alternatively, you could guarantee an existing object path with a suitable
> interface at the caller's connection. An object path that can be inferred
> uniquely from the Job ID.

hm. right.. because a message has the "return address" on it, right? so as 
long as the path is always, say, /IOJobs/[JobID] we would be covered?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]