• Replies 6 replies
  • Subscribers 247 subscribers
  • Views 57 views
  • Users 0 members are here
Related

API Session Best Practices

Darrin Katz
$organization

Hi everyone,

We're looking at cleaning up our legacy session handling code used by our websites. I just wanted to ask the community if they have any specific recommendations for best practices regarding how to manage the session key, session variables, and session timeouts on your websites.

I've taken a look at the documents in the "Web API Documentation" for v9.0, so I'm looking for advice that goes beyond what is covered there.

Thanks!

Darrin Katz Programmer/Analyst

Soulpepper Theatre Company

T 416.203.6264 x.182
F 416.203.1531
W soulpepper.ca


Young Centre for the Performing Arts
Distillery Historic District
Box Office 416.866.8666

 



[edited by: Darrin Katz at 11:49 AM (GMT -6) on 13 Oct 2009]
  • $organization
    As a follow up, I was wondering if there is any point to maintaining a local hashtable on the webserver side, as opposed to just going directly to the Tessitura database every time you need to set or get a session variable.
     
    Thanks again!
    Darrin

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Darrin Katz
    Sent: Tuesday, October 13, 2009 12:52 PM
    To: darrin@soulpepper.ca
    Subject: [Tessitura Web Forum] API Session Best Practices

    Hi everyone,

    We're looking at cleaning up our legacy session handling code used by our websites. I just wanted to ask the community if they have any specific recommendations for best practices regarding how to manage the session key, session variables, and session timeouts on your websites.

    Thanks!

    Darrin Katz Programmer/Analyst

    Soulpepper Theatre Company

    T 416.203.6264 x.182
    F 416.203.1531
    W soulpepper.ca


    Young Centre for the Performing Arts
    Distillery Historic District
    Box Office 416.866.8666

     




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
  • $organization

    Darrin, I’m not sure if this is what you are looking for, but there is a new procedure in version 9 called UP_CLEAR_WEB_TABLES.  This is an optional utility which will remove data from the web tables which may be old or out of date.  This may be desirable particularly if there is a large volume of web sales as the web tables can become quite large.  I would suggest you take  a look at the Version 9.0 Highlights documentation and in particular the section entitled ‘Utility to Clear Old Data from Web Tables’ which documents this procedure.

     

    Gregg

     

     

     

    cid:image002.jpg@01C9C41F.7B304100

    Gregg Stickney

    Application Support Specialist/Manager Knowledgebase

    Tessitura Network

    www.tessituranetwork.com

    gstickney@tessituranetwork.com

    +1 (888) 643-5778, ext. 318 (Office)

    +1 (330) 835-4507 (Fax)

    +1 (216) 469-7533 (Mobile)

    +1 (888) 643-5778, ext. 201 (Support Line)

     

     

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Darrin Katz
    Sent: Tuesday, October 13, 2009 12:52 PM
    To: Gregg Stickney
    Subject: [Tessitura Web Forum] API Session Best Practices

     

    Hi everyone,

    We're looking at cleaning up our legacy session handling code used by our websites. I just wanted to ask the community if they have any specific recommendations for best practices regarding how to manage the session key, session variables, and session timeouts on your websites.

    Thanks!

    Darrin Katz Programmer/Analyst

    Soulpepper Theatre Company

    T 416.203.6264 x.182
    F 416.203.1531
    W soulpepper.ca


    Young Centre for the Performing Arts
    Distillery Historic District
    Box Office 416.866.8666

     




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • $organization in reply to Gregg Stickney

    Hi Gregg,
     
    Thanks for pointing this out.
     
    When I said "cleaning up our legacy session handling code" I was referring to the logic used by our websites, not the session data stored in our database. We inherited a lot of code that needs to be revised, which is why I'm asking the community for their input.
     
    Thanks again,
    Darrin


    [edited by: Darrin Katz at 1:37 PM (GMT -6) on 15 Oct 2009]
  • $organization in reply to Darrin Katz

    Hi Darrin,

    I'm not sure I understand exactly what your situation is. But as a general rule, the more you can store/cache on the web server's end, the better. The fewer calls you need to make back to the API server, the faster your site will run.

       -Morgan

  • $organization in reply to Morgan L'Argent (Past Member)

    Hi Morgan,
     
    Thanks for getting back to me about this. Yes, I can see why storing a hashtable on the web server would improve performance, that should have been obvious to me.
     
    With regards to clarifying my situation, the legacy code we've been using for session management is a little buggy and, though I'm going to go through and clean up specific problems, I was looking for general advice with regards to managing Tessitura web sessions. If generic best practices for web sessions applies equally to web sites connecting to Tessitura, then so be it, but I thought it couldn't hurt to ask.
     
    Thanks again,
    Darrin


    [edited by: Darrin Katz at 1:36 PM (GMT -6) on 15 Oct 2009]
  • $organization in reply to Morgan L'Argent (Past Member)

    Darrin, I agree with Morgan. We store session variables ont he web server. This way it is much quicker to access and is less problematic than storing it all in cookies.

    Christian