Chris,
I can not answer all of your questions, but I hope this helps.
ARS API (by design) should work with previous versions. ( Unless there
is some major change that requires a "break" to happen. Which should
be avoided where possible and mostly limited to "Security" type
issues.)
So in all likely hood ARSPerl v1.85 was written (or last updated/test)
when v6.3 was the "latest version". I doubt anyone from the project
has really tested against v7, but I would expect it to work. (And I
would also expect to do my own testing of it too.) The extent to which
you need to test depends on what parts of ARSPerl your using.
I can also comment on the "encrypted connections" part with respect to
an v6.3 ARS server. There are some "ARSPerl compile time settings"
that you need to get the encryption libs in place. Other than that, it
has worked well for us. I hope that v7 does not bring us any new pain
points. ( I have not noticed any changes in the C layer that look
alarming to me. So I expect no issues with v7 API specifically, but I
could have missed something too.)
HTH.
--
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 10/24/06, Chris Smith <chr...@du...> wrote:
> Hello,
> I was curious if anyone is using arsperl with ARSv7.0.
> We are in the process of an upgrade and I notice that arsperl.org lists arsperl 1.85 as supporting up to ars6.3 API.
> Will it work with 7.0 API limited to 6.3 functions?
> Will it work at all?
> I will also be running Remedy encryption configured to require encrypted connections. If anyone has any comments on that I would like to hear them too!
>
> Thanks,
> Chris Smith
|
