IMO the two projects could share a private library for interacting with MetaService and use its operations. Something like:
MetaService* s = MetaService::connect( "/tmp/metaservice_socket" ); Job* j1 = s->addRedirection(...); Job* j2 = s->loadEmbeddedJolieService(...); [...] For instance, by using addRedirection one could expose a local C++ service with any of JOLIE's supported protocol (that's a plasma use-case). By using loadEmbeddedJolieService one can make use of JOLIE adapters (as I described in my last mail in the jolie+plasma api discussion thread). Again, by using addRedirection one could also put in place "service access" to an external service (web service, rest service or whatever), etc.. 2009/1/27 Aaron J. Seigo <[email protected]> > On Monday 26 January 2009, Fabrizio Montesi wrote: > > today igorto and vkrause (akonadi people) jumped in #jolie to speak about > > the possibility to integrate akonadi with Jolie. They're still > > investigating, but the thing surely seem possible and sound. I think that > > the best thing to do would be to share as much information and work as > > possible.. no reason to have duplicate work, libraries or whatever comes > > up. So my point is: where do we discuss? > > i'm on both the kde-pim as well as the plasma list. don't know though, what > kind of cross over would there end up being between akonadi and plasma's > usage > of jolie i wonder? > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Software > > > _______________________________________________ > Plasma-devel mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/plasma-devel > >
_______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
