I'm a bit confused now, should I declare the BloodhoundRPC plugin as a dependency then? Or should I mention in my api that the query() and changeLog() methods were created by Olemis?
Thanks, Antonia On Thu, Jul 18, 2013 at 9:38 PM, Olemis Lang <[email protected]> wrote: > On 7/18/13, Joachim Dreimann <[email protected]> wrote: > > On 18 July 2013 04:55, Olemis Lang <[email protected]> wrote: > >> On 7/17/13, Antonia Horincar <[email protected]> wrote: > >> > Hi, > >> > > >> > >> :) > >> > >> > Sorry for the late reply. By using the two methods mentioned above > >> > (changeLog and query) I managed to get what I wanted. However, I'm not > >> sure > >> > if I'm supposed to integrate the entire Bloodhound RPC plugin in my > >> > project, or just extract the methods? > >> > > >> > >> I recommend to declare Bloodhound RPC plugin as a dependency in > >> setup.py just like any other (Python) library you might choose to > >> build your project. There is a case for including it in default > >> installation (eventually) e.g. quick ticket shortcut in Bloodhound > >> theme . > >> > > > > I seem to remember there was also a case against it previously > > I can not find the exact messages but now I recall this might be the case . > > > - how has > > that been addressed? > > > > We have not had discussions on the subject recently. Nevertheless if > the solution implemented by Antonia will cover (eventually) any > objects in core then she'll end-up doing one of two things : > > - Reimplementing the very same RPC methods > - Copying almost all RPC methods > * Should improvements be committed in Bloodhound RPC > plugin those modifications will be hard to maintain > > trachacks:XmlRpcPlugin may be used as a data access layer by core and > plugins . That's the case even for trac-dev (citation needed) > > -- > Regards, > > Olemis. >
