Re: [Arsperl-users] Using ARSPerl to Build a Web Interface

[Carey M. B. <bla...@gm...>]

Mike,

Ref:
http://www.webopedia.com/TERM/S/session_cookie.html
http://www.allaboutcookies.org/cookies/session-cookies-used-for.html
http://searchwebservices.techtarget.com/sDefinition/0,,sid26_gci752450,00.html


IMHO... this is a bad way to keep state for a web site. It is client side
and could present security concerns if your browser is flawed. (Like maybe
the most popular choice... IE.)


If I were you... I would start at a better staring point. Try the Java API
and go to the JSP/Servlet model for this approach. And here are just a few
reasons why:

1) Most ARS customers will have a web server capible of being a Mid-tier
server. (And your interface might be helpful in some cases in addition to
the Mid-Tier.)
2) JSP/Servlets are a "later generation" and approach the web with more
security options by design than CGI's ever had.
3) The Java API will be supported by BMC. ARSPerl never has been directly
supported by Remedy or BMC.
4) The new Java API is reported to be "totally Java" (no more JNI layer) and
that will make such a web interface as portable as any JSP engine out there.
And that will be more portable than any ARSPerl interface could be because
it will still be (as far as I know) a wrapper around the C API that has
limited platform support.

But that might be more work than your interested in too. ( I just think it
is a much better path to go down if you have any time to spend on such a
major undertaking.)

HTH.

AND just to be clear... ARSPerl is great. It has served a very needed niche
in the ARS universe for years and I expect it to continue to do so. A
command line Perl script is likely faster than a command line Java program.
However, there are support and maintenance issues to sort out too. So for
server side command line scripting... ARSPerl is still a good choice. Time
will tell if the new Java API can put a dent in that niche or not. ( And
given the Filter plugin options... command line interfaces mostly should be
moved into that universe anyway.)

-- 
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/26/07, Mike Wallick <mdw...@gm...> wrote:
>
> Forgive me for being dense, but I don't understand how one would tie a
> control record that was created from a login routine, for example, to a
> session ID or similar. Given a session ID, how does one tie that to a
> control record that has already been created/validated?
>
> In other words, where does the control record "live" and how does one get
> at it? Doesn't the control record "disappear" once the web server request is
> complete?
>
> Mike