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

Protected session variables question

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

    Protected session variables question

    My limited understanding of these is that they are (or were) available to both hide them from the end user and to stop the end user from changing their values. Documentation states that from v12 all session variables are protected to stop the end user from changing them. My question is therefore, are all session variables (from v12) also hidden from the end user.
    Thanks
    Terry

    #2
    Re: Protected session variables question

    You're correct. There's no difference now between session.MyVar and session.__protected__myVar. There used to be functional differences, but now all that's really different between them is their name.
    -Steve
    sigpic

    Comment


      #3
      Re: Protected session variables question

      There is an easy way to create session variables directly from URL and change their values also so if you want end user to change value they can do it easily. This is also possible using ajax.

      (I have noticed that AA handles differently session.variable and session.__variable__ but they function same way in the end)

      Comment


        #4
        Re: Protected session variables question

        I was just trying to establish that I no longer needed to use __protected__ in order to make sure the end user could neither see or change the session variable.
        Thanks

        Comment


          #5
          Re: Protected session variables question

          http://wiki.alphasoftware.com/~alpha...cted+Variables

          please see this discussion, as of version 11 all session variables are protected, no need to protect it yourself.
          as far as i know the user will not be able to change it, you need to change it yourself.
          thanks for reading

          gandhi

          version 11 3381 - 4096
          mysql backend
          http://www.alphawebprogramming.blogspot.com
          [email protected]
          Skype:[email protected]
          1 914 924 5171

          Comment


            #6
            Re: Protected session variables question

            This was the Documentation I was referring to in my original post, but it does not mention if the variables are also hidden from the end user.
            Thanks
            terry

            Comment


              #7
              Re: Protected session variables question

              Originally posted by GGandhi View Post
              [url]as far as i know the user will not be able to change it, you need to change it yourself.
              As I mentioned before it is easy to change this behavior. Then user just uses query strings to change value of session variable(s) or creates new session variable(s).

              Comment


                #8
                Re: Protected session variables question

                Originally posted by Terrymorgan View Post
                I was just trying to establish that I no longer needed to use __protected__
                You do not need the __protected__
                Mike Brown - Contact Me
                Programmatic Technologies, LLC
                Programmatic-Technologies.com
                Independent Developer & Consultant​​

                Comment


                  #9
                  Re: Protected session variables question

                  Originally posted by kkfin View Post
                  As I mentioned before it is easy to change this behavior. Then user just uses query strings to change value of session variable(s) or creates new session variable(s).
                  Ken, as of V11, the query string cannot directly create or modify session variables. This is why the "__protected__" naming convention is no longer needed.

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

                  Comment


                    #10
                    Re: Protected session variables question

                    Originally posted by Lenny Forziati View Post
                    Ken, as of V11, the query string cannot directly create or modify session variables. This is why the "__protected__" naming convention is no longer needed.
                    I know that but you can bypass restriction . With this code you can create or modify session variables using query strings. This is most simple example.

                    Code:
                    session.init = "yes"
                    property_from_url(session,Request.QUERY_STRING)
                    Is this wise is another question but I use this technique in some cases.

                    Comment

                    Working...
                    X