Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Session variables

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Session variables

    Can different users logged in to an application at the same time, have session variables with the same name, but different values?
    Further explanation. User one logs in to application and the Login_Processing_Page dims session vars, size, color, weight, which will be assigned values during application use.
    User two logs in and the Login_Processing_Page dims the same vars, size, color, weight, which will be assigned values during application use, but these values are not the same as user one's variable values.

    Will these session variables for both users retain their individual values and remain segregated from affecting each other?

    Thanks
    John

    #2
    Re: Session variables

    Each user logging in, does so in a different session. The Session value is assigned to the session. Different sessions, different values.

    So, Yes each users session variables are segregated from each other.

    Also, if you log in with Internet Explorer and also login to your A5 Application with Chrome and Firefox at the same time ( 3 different logins ), you will have 3 different sessions and three different sets of session variables that are independent of each other.

    Hope that helps.

    Comment


      #3
      Re: Session variables

      Just to add to Paul's reply, "Each user logging in, does so in a different session."
      The session variables are only on the local machine. "So, Yes each users session variables are segregated from each other."
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment


        #4
        Re: Session variables

        Originally posted by Keith Hubert View Post
        Just to add to Paul's reply, "Each user logging in, does so in a different session."
        The session variables are only on the local machine. "So, Yes each users session variables are segregated from each other."
        No, the session variables are on the server, which is where all Xbasic is executed. They are however kept distinct as explained by Paul.

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation

        Comment


          #5
          Re: Session variables

          Lenny, Thanks for the clarification.
          Regards
          Keith Hubert
          Alpha Guild Member
          London.
          KHDB Management Systems
          Skype = keith.hubert


          For your day-to-day Needs, you Need an Alpha Database!

          Comment


            #6
            Re: Session variables

            One note John,

            If you are storing non-critical, low security properties that are used mainly for client-side purposes, then you should consider just setting them to global javascript vars instead.

            e.g.
            if (typeof window.JohnsVars==='undefined') { window['JohnsVars'] = {}; }
            JohnsVars['size']='large';

            The javascript global called JohnsVars (and therefore everything within in) will then be available client-side everywhere, anytime. You can also easily pass it back to the server as needed.

            Regards,
            Andy.

            Comment


              #7
              Re: Session variables

              Andy,

              That is interesting. Could you please explain the advantage of storing as global java script vars vs session variables?
              Gary S. Traub, Ph.D.

              Comment


                #8
                Re: Session variables

                Originally posted by drgarytraub View Post
                Andy,

                That is interesting. Could you please explain the advantage of storing as global java script vars vs session variables?
                You should never point to a var global even at low risk with information that represent a name,number to lower and avoid the risk of cross side scripting.
                It's better to have 3 more "private" server side stored sessions then one global the could be a risk.
                If anyone can manipulate that "global" your hot!


                m2p

                Comment


                  #9
                  Re: Session variables

                  Hi Gary,

                  Session vars are server-side variables as they only exist within the A5 environment. Each different computer/user can be uniquely identified by the server, and variables relating to each person stored.

                  Javascript global vars exist within the browser's scope (all windows and their children popups) but can't be seen by the server unless passed via a callback, posted in a field, etc.

                  Any private or security-related information (like UserID) should be server-side vars because a client could easily change the contents of a javascript variable or HTML field and thus fool the server.

                  There are many different ways to bring variables from the server environment to the client environment (and vice versa), and I'm only saying that if you are not granting access or performing any other sensitive operations via session variables, then another option is to set a global JS variable (in your first a5w page or component after login, for example). This can make lots of sense if all your manipulation is client-side and in javascript functions or conditional tests. It is just easier, that's all.

                  Search the message board for more info - there is good stuff in there.

                  Regards,
                  Andy.

                  Comment

                  Working...
                  X