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

HTTP Connection Close

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

    HTTP Connection Close

    Hi,

    I have an Updateable Grid.
    I set http_get() on AfterInsertRecord xbasic function.
    It's run well.

    The problem is if I insert again fast enough (immediately after the first insert), the http_get() is not running.
    It looks like it's waiting until time out then the http_get() can run again after I insert the data.

    My question is, does Alpha have http.close() or something like that to close the connection?

    Thanks,
    Antony

    #2
    No, there isn't a close method. That isn't needed. By default the connection will timeout after 8 seconds OR the server will respond with something before that timeout. Have you looked at Alpha's documentation? I linked it below. I would recommend debugging your method and see what the server response is.

    https://documentation.alphasoftware....20Function.xml
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Hi Mike, thank you for your answer.

      I have read the documentation and there's no info about the close method.
      I do the debug and yes, http_get catches immediately of the previous session, not the new one.
      and 1 other thing, I use http_get for calling API, the response can be longer than 8 seconds, so I make the timeout longer (I set it to 60 because the process varied from 5 to 25 and could be longer).

      I just use the simple code on xbasic :
      dim p as p
      p = http_get(apiLink, "", 80, 60000)

      Comment


        #4
        http_get() is a synchronous (blocking) function and it automatically closes the connection once the response is received, or upon timeout if that occurs before the full response is able to be read.

        It sounds like you are attempting to run the function a second time while the first execution is still running. Because it is a blocking call, no other Xbasic can execute at that time, so attempting to execute another http_get(), or any other Xbasic, will need to wait until the first call has completed.

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

        Comment


          #5
          In the first function that makes the first call - call the second function in the onComplete of the first function. - always worked for me.
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)

          Comment


            #6
            Originally posted by Lenny Forziati View Post
            http_get() is a synchronous (blocking) function and it automatically closes the connection once the response is received, or upon timeout if that occurs before the full response is able to be read.

            It sounds like you are attempting to run the function a second time while the first execution is still running. Because it is a blocking call, no other Xbasic can execute at that time, so attempting to execute another http_get(), or any other Xbasic, will need to wait until the first call has completed.
            I did some time ago a test and you can solve this waiting problem. So something like asyncronous Xbasic. Check this thread post 7.

            Comment


              #7
              Originally posted by Lenny Forziati View Post
              http_get() is a synchronous (blocking) function and it automatically closes the connection once the response is received, or upon timeout if that occurs before the full response is able to be read.

              It sounds like you are attempting to run the function a second time while the first execution is still running. Because it is a blocking call, no other Xbasic can execute at that time, so attempting to execute another http_get(), or any other Xbasic, will need to wait until the first call has completed.
              I call the http_get() on afterUpdateRecord xbasic function.
              and have it processed until return to the end.

              and then I update the record again, so it'll run the same HTTP inside the http_get() but it is just like having a session from before.

              Comment


                #8
                Originally posted by kkfin View Post

                I did some time ago a test and you can solve this waiting problem. So something like asyncronous Xbasic. Check this thread post 7.
                sorry, but I don't really understand how to use it.

                Comment


                  #9
                  Originally posted by tibanker View Post

                  sorry, but I don't really understand how to use it.
                  It is just an example that shows how to bypass the xbasic execution tube which Lenny mentioned.

                  So because Alpa has nodejs integration and Alphas nodejs service can interact with xbasic and nodejs runs javascript you can this in mind send so called Beacon also in Alpha . The xbasic that calls Alphas nodejs service needs not to wait the Nodejs services (javascript but which actually calls xbasic ) result so you are sending Beacon and the calling xbasic can continue immediately. So the example just shows that this all also works in practice. It is not related to your problem in your thread. You can forget the post.​

                  Comment

                  Working...
                  X