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_get_page2

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

  • #16
    Re: http_get_page2

    Tom:
    Yes the page, like many others, almost all others, are built dynamically but that has nothing to do with the page info. That's static until the web designer changes it. The scripts that trigger those other parts of the page, those scripts are part of the page info and you should be able to see them.

    These functions evidently aren't doing the job. I haven't tried others but I am not sure why does the client want to copy the page info? For what use?

    Comment


    • #17
      Re: http_get_page2

      Tom,
      Have you tried http_get_page2() with

      "include_headers" = .t.

      ?

      The default is .f.

      Comment


      • #18
        Re: http_get_page2

        Garry,
        HTTP_GET_PAGE() obtains the headers by default and does not obtain the "Includes" that are missing.....using the header argument in the HTTP_GET_PAGE2() function actually delivers a bit less information....

        This sure seems to be something that will be wanted by possibly many and hopefully a way is found to get around the apparent limitation that is imposed by some websites.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


        • #19
          Re: http_get_page2

          Tom,
          In my earlier post I should have written http_post_page2() not http_get_page2().

          So have you tried http_post_page2() with

          "include_headers" = .t.

          ?

          Comment


          • #20
            Re: http_get_page2

            Thanks all.

            Further digging here indicates that maybe this is a timing issue. I'm trying to retrieve the source html from the specified web page and then parse it. This is happening in a script since I'm trying to automate the sequence. I'm beginning to think maybe, just maybe, what's happening is that my script is beginning to parse the source text before it's all been downloaded. Since my script looks for markers in the source text that are near the bottom of the web page its returning my "not found" error trap, probably well before the source itself has been completely downloaded. Is this possible?

            What's odd is that week before last it ran cleanly.

            Anyway, I'm going to move the "get source" routine to a separate UDF to isolate it from the script. Will let you know what I find. Thanks again.

            Later on ...

            Yes, that did the trick. I changed the script to have it call a UDF. The only thing the udf did was get the source html using http_get_page2(), and return it in a char variable. My script then waited for the function to do its work before beginning my parse routines.
            Last edited by Tom Cone Jr; 08-23-2010, 06:24 AM. Reason: Update findings

            Comment


            • #21
              Re: http_get_page2

              Originally posted by Tom Cone Jr View Post
              Yes, that did the trick. I changed the script to have it call a UDF. The only thing the udf did was get the source html using http_get_page2(), and return it in a char variable. My script then waited for the function to do its work before beginning my parse routines.
              That should be a point of general interest. It's something I've suspected for a long time but haven't bothered testing.

              Apparently UDFs will wait until everything inside has completed before returning control to the calling script/function but A5 built-in functions do not necessarily operate the same way. The issue described above seems to indicate that at least some A5 functions will return control to the calling script before they have completed their task; i.e., all functions are not created equal!

              It would be interesting to know which built-in functions act this way. It may be the reason for all the weird, totally random crashes in my most complex application.

              Comment


              • #22
                Re: http_get_page2

                I have run across/mentioned this in the past as well....I remember an Alpha function that even was inconsistent in how it acted...sometimes would finish prior to the next and other times not.....I now assume that none but UDFs work in succession in order to make certain aspects of an application more bulletproof.
                Mike
                __________________________________________
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau
                __________________________________________



                Comment


                • #23
                  Re: http_get_page2

                  Originally posted by CALocklin View Post
                  TThe issue described above seems to indicate that at least some A5 functions will return control to the calling script before they have completed their task; i.e., all functions are not created equal!
                  Not sure how you arrived at that conclusion?
                  Originally posted by MikeC View Post
                  I have run across/mentioned this in the past as well....I remember an Alpha function that even was inconsistent in how it acted...sometimes would finish prior to the next and other times not.....I now assume that none but UDFs work in succession in order to make certain aspects of an application more bulletproof.
                  Never heard that dog bark before! Would like to see an example.

                  Comment


                  • #24
                    Re: http_get_page2

                    If I remembered what it was I would have given it when I posted...seems familiar when attempting some API/Windows work using Alpha to obtain info but cannot place the exact function.

                    The main point is that some Alpha functions halt the code and some don't.....and that the documentation usually does not specify which (although sys_shell() does inform us that your scripts will continue to run). UDFs, at least all that I have created, seem to run one at a time--using UDFs have cured an enormous amount of timing issues I have had in my work.
                    Mike
                    __________________________________________
                    It is only when we forget all our learning that we begin to know.
                    It's not what you look at that matters, it's what you see.
                    Henry David Thoreau
                    __________________________________________



                    Comment

                    Working...
                    X