That PPKey-FTP was an implementation between 3 Web sites of 3 companies. On my side, I did have a scheduler colling the service; for others - it looked like my service generated FTP load periodically.
I would like to work with you that time (back to 2001) in one of those companies, it would save ma a lot of nerve cells. Cheers, - Michael ________________________________ From: Rob Eamon <[email protected]> To: [email protected] Sent: Friday, January 30, 2009 4:46:24 PM Subject: [service-orientated-architecture] Re: [ZapFlash] Batch Processing with SOA I think batching is not the service. I think it is a characteristic of an interface to the service. For your FTP example, do you mean the service put new PPKeys out to one or more FTP servers periodically? The scheduling aspect was touched on briefly in other threads as I recall. Should scheduling be part of a service or is it external? IMO, it is better to use an external scheduler. In your PPKeys example, the scheduler would invoke the PPKeys service via the appropriate interface. The interface would accept 1 or more destinations for the PPKeys file(s). The service would then put the PPKeys file to the destinations indicated by the invocation. The scheduler in this case is the "application frontend" and the service itself has no idea that every 10 minutes keys are supposed to be sent to various FTP servers. Thoughts? -Rob --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <m3pou...@.. .> wrote: > > If not all questions are addressed to Steve, I would say that > batching may be both - service and service feature, though I prefer > the latter. For "Billing Service", it might be an FTP-based > interface, for example. > > I had such thing once - I built a PKI-based system where new PPKeys > might be obtained by participants on-demand (Web Service interface) > as well as via FTP channel (interface) where the service posted the > keys on a schedule. > > - Michael
