On 8/2/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > > On 8/1/07, Paulo Sergio <[EMAIL PROTECTED]> wrote: > > On 8/1/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > > > > > > On 8/1/07, Paulo Sergio <[EMAIL PROTECTED]> wrote: > > > > On 8/1/07, Robert Burrell Donkin <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > On 8/1/07, Paulo Sergio <[EMAIL PROTECTED]> wrote: > > > > > > On 8/1/07, Robert Burrell Donkin <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > > > > > > On 7/31/07, Paulo Sergio <[EMAIL PROTECTED]> wrote: > > > > > > > > Thanks for the fast answer.. it is working now ! > > > > > > > > i'm now trying to add a web service client to imap function > > > (this > > > > > web > > > > > > > > service will be the repository). > > > > > > > > > > > > > > you may find that binding IMAP to web services is an > interesting > > > > > problem > > > > > > > ;-) > > > > > > > > > > > > > > SOA or REST? > > > > > > > > > > > > > > > > > > SOA.. > > > > > > > > > > asynchronous? > > > > yep > > > > > > just for the repository-push parts of the specification or do you plan > > > to use SEDA for the repository access? > > > > > > as this project is yet an experience, i don't know yet witch parts will > use > > the web service, but for now it should be only for the repository parts. > > I don't know much about SEDA (just that it is a architecture to handle > a > > huge number of concurrent services). > > just wondered whether you had it in mind to use asynchronous or > synchronous messaging for the repository access
i will use the web services for authentication and message/folder operations > > (i have long term interests in REST based mail protocols) > > > > > > > > > > > but why do you say "interesting problem"? > > > > > > > > > > IMAP is an interesting protocol in many ways > > > > > > > > > > it makes many functions which should be simple, complex instead > > > > > > > > > > > my idea is not bind all IMAP commands to web services, just the > > > > > repository, > > > > > > authentication and maybe just a few more > > > > > > > > > > will the repository be shared? > > > > > > > > > > > > yep > > > > this work is just an experimentation with adding Imap support to an > > > existing > > > > framework, and the web-services seem to be the right way to connect > > > both > > > > systems > > > > > > sounds like a good reason to me ;-) > > > > > > are you working to existing web service APIs? > > > > > > what do you mean? i'm working with a web service that i'm developing... > > 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.. Paulo F. > - robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
