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



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

concurrent users

  • Filter
  • Time
  • Show
Clear All
new posts

  • concurrent users


    I have code on an a5w page that opens an img ref photo, opens a table to get another photo, grabs another photo from the root, and merges these 3 photos together, then saves the result jpg in a folder named after a piece of data in the original photo's table. The resulting photo path and filename are saved in another table, then a grid displays these photos.

    This code loops through a table 29 more times to make and save more photos.
    It seems to take 12 - 15 seconds to complete the procedure and display the grid.

    This procedure works very well

    Unless 2 or more users are doing this at the same time
    Some of the images from the subsequent user are being placed in the first users records. And they aren't happy.

    Obviously I don't know how to keep users separated in this web stuff

    Any ideas on what I'm missing?


  • #2
    Re: concurrent users

    Obviously I don't know how to keep users separated in this web stuff
    Who does Duane, who does.
    I have a similar process on a site to what you have, but know where near as complex.
    A. I make use of each users session folder, not only does this remain separate but the App server cleans it up when the session expires.
    B. Always remember that the App-Server runs basically in a stateless manner, eg it remembers zilch from the last code page run, Thus you need to write stuff into temp tables or files or special server or session vars, if you wish to refer to it later.

    Unless 2 or more users are doing this at the same time
    In writing this, I would look at keeping everything on one code page.
    I'm not 100% on this but I believe the AppServer only processes one page at a time, thus, the 2nd user would have a short wait. Also make sure that the session variables are not at all shared.


    • #3
      Re: concurrent users

      Every user on your website has a unique folder belonging only to them. The name of the folder is in the variable session._session_folder. If you perform your process using that as the work area, everything will stay separate. When their session expires, the folder and contents will disappear.

      Also, when it comes to images, you might look at ImageMagik. It can process images with command line tools, to do just about anything. The HELP for ImageMagik is awful, but here is an example that uploads an image, and in the last stage creates PNG thumbnails using ImageMagik.

      'session.mod = mod
      dim session.im1 as c
      if eval_valid("cmd")
      	if file.exists(fldr) = .f.
      	end if
      	IF FileToUpload.filename<>""
      		filename = fldr + "\\" + FileToUpload.filename
      		if file.exists(filename)
      		end if
      		newfilename = fldr + "\\" + + ".jpg"
      		if file.exists(newfilename)
      		end if
      		newthumb	= fldr + "\\" + "th_" + ".png"
      		shelltask = fldr + "\mk.bat " + fldr + " " + + " " + "" 
      		im = path + "\\" + "th_"".png"
      ?"No file to upload"
      	end if
      end if
      The MK.BAT looks like this:

      c:\progra~1\imagem~1\convert.exe %1\%2.jpg -auto-orient -thumbnail 200 -unsharp 0x.5 %1\th_%2.png
      Steve Wood
      There is no Cloud. It's just someone else's computer.
      Web - Mobile - Hosting - Products - Frameworks - Developer Resources
      AlphaToGo | IADN (100% Alpha Anywhere Websites)


      • #4
        Re: concurrent users

        Thanks for the replies guys

        Deep down inside I knew I should be playing with session folders. I had to do that once before using javascript to keep photos organized between clients. But this time I was kinda foggy and wasn't sure how to procede with that, so the method I took was faster to me.

        And now I'm paying the price.

        I have the routine's code on one page and as a precaution I'm trying to use a variable = t and f to let people through the code or to wait and check the variable value again (doesn't seem to work very well). I don't think any of these session variables are shared, although I'm not really sure how to share them or not to.

        I will have to design it properly when I can get to it in a few months and hope not too many clients have photos colliding in the mean time.

        Steve, thanks for the IM code. Been looking at that pgm for another purpose for a while trying to get it figured out. Never thought about using it for this web purpose. Probably would have been better since it wouldn't be using the A5 blob variable bitmap confusing way that I have been. There wouldn't be any blobs getting mixed up between clients, I figure that is what has been happening - the blobs are getting replaced by the newer request.