Ray, Any ARS API based client is limited to the OS's where that API is supported. A Web Service interface would not share that restriction.
So assuming that the target OS is a supported OS, then either works about the same for submit operations. The only other advantage(maybe) that I can think of with the Web Services interface is that your Mid-Tier might have a pre-configured "anonymous" user that the WS client could "use" while the API interface would be required to supply username/password information too. However I doubt that you really want to make a WS that can create a ticket and be accessible to anyone who can find your Mid-Tier. So it is likely a mute point. :) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 6/20/07, Ray M <[EMAIL PROTECTED]> wrote:
Hi: I have to make a decision whether to submit ticket creation and update using Webservice or ARSPerl. I am leaning towards ARSPerl just b'cos it's much simpler to code and any changes in the form will involve a minor change in the ARSPerl code. Wondering if there is anything I will miss going with ARSPerl instead of Webservice. TIA Ray
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
