[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [trans-ws] Re: Notification information[Scanned]
Bill, Our service works by the client polling our server. They can set a polling frequency within acceptable bounds. A 'CompletedFiles' message is sent, that returns a list of the references to files that are now complete. The client need only poll when necessary (when there are outstanding files), and most of the time the response is empty, i.e. there are no files ready for collection. This works very well, and since all poll messages are very small, the server performance is not affected. E mail seems a bit 'un-automated', and strays off the web service, and to insist on a client having a web service in return expands the deployment time, and will limit the use. The nice thing about sticking to the single web service with polling is that all messages are in the same form so the client's integration job is easy and the firewall settings are probably already in place. Any comments would be greatly appreciated. Regards Ian Ian Harris Technical Director thebigword 20 Wood Lane Headingley Leeds LS6 2AE tel (direct): +44 (0) 870 748 8058 mobile: +44 (0)7710 318477 fax: +44 (0) 870 748 8001 -----Original Message----- From: Bill Looby [mailto:bill_looby@ie.ibm.com] Sent: 14 March 2003 09:54 To: trans-ws@lists.oasis-open.org Subject: [trans-ws] Re: Notification information[Scanned] I'm afraid the Notification section was a phantom section I'd intended to add (hadn't realised I still referred to it). Sorry. Essentially what it amounts to, is dealing with the fact that a Web Service is a client initiated interface, so there's no obvious way for the server to "push" information back. The way I see it there are two primary options in this regard - 1. Email notification A return email address could be presented by the client, when accepting the quote. There would then be a standard notification message sent (we would have to define the format, which would include the job ticket) to this address on job completion (or on job error ? query ?) 2. Presentation of a return Web Service We would have to define another standard service that could be offered by a client for return notification. The idea is that the client would simply have to supply the URL at which this service is available. This is more flexible, but many users may not be in a position to supply it. There are two reasons for this - Smaller users may not be hosting their own sites, or may not even have a fixed URL Corporate users may have a large security overhead in presenting an external web service Most workflows should be able to work off email notification, but it's low-tech and can be awkward. Probably a requirement to support this for lower tech users however, even if we do the return service aswell. Regards, -Bill. ____________________________________ Bill Looby Architect, Web Globalisation Technologies Dublin Software Lab IBM Ireland Phone (Internal) : 166796 Phone (External) : +353 1 7046796 ____________________________________ "Reynolds, Peter" <Peter.Reynolds@bown To: "'bill_looby@ie.ibm.com'" <bill_looby@ie.ibm.com> eglobal.ie> cc: Subject: Notification information 13/03/2003 16:21 Hi Bill, The Trans-WS TC was looking at the rtf which you forwarded in January and could not find the 'Notification information' mentioned in the mail. Can you explain to the TC what this means. Thanks, Peter. Peter Reynolds, Software Development Manager Bowne Global Solutions 3, West Pier Business Campus, Dun Laoghaire, Co. Dublin, Ireland Tel: +353-1-202-1280 Fax: +353-1- 202-1299 Peter.Reynolds@bowneglobal.ie Web Site: http//www.bowneglobal.com http//www.berlitzIT.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]