kuiserver future (to gui or not to gui)

[Aaron J. Seigo]

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)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070222/8f836925/attachment.sig>