On 8/2/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > > On 8/2/07, Paulo Sergio <[EMAIL PROTECTED]> wrote: > > On 8/2/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > > <snip> > > > > just wondered whether there are existing web services you need to > > > interface to or whether you plan to develop an API from scratch > > > > > > i'm developing an api from scratch because i need to adapt it to my > > backend, i will hook the service at a higher level, and replace the > > repository calls using the web service, again: as this is just an > experiment > > things can change :) > > > > > > the reason why i ask is that i've had it in mind for a while to take > > > another look at the repository API: it's very big and general. i'd > > > like to present a more compact API to the processor code so that it's > > > easier to create alternative repository implementations. > > > > > > An easy (and compact) API will probably make integrations with existing > > backends easier. But in my specific project i believe that not using > this > > layer (repository) is a good option.. or maybe not if we think about > > scalability.. > > so, i guess you'll be reimplementing the processing layer then?
good question.. i don't know yet.. where do you think it would be the right place to insert the web service methods? do you think i will need to reimplement the processing layer? Paulo F. - robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
