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

Difficulty replicating WebSockets demo...

  • Filter
  • Time
  • Show
Clear All
new posts

  • Difficulty replicating WebSockets demo...

    I followed the web sockets video tutorial to the letter (as far as I can tell) but when I send a message, the receiving browser displays an alert saying: "Received a message that was not in correct format. Messages must be JSON strings".

    The local instance of the list in each browser updates as expected with its own message that was attempted to broadcast.

    As the video shows, I entered the following into the button click event, with an additional alert "alert(JSON.stringify(obj));" to see what is being sent:

    var _name = {dialog.object}.getValue('name'); 
    var _message = {dialog.object}.getValue('messageText');
    if (_name == '') {
    	alert('Please Enter Your User Name.');
    	return false;
    if (_message == '') {
    	alert('Please Enter a Message.');
    	return false;
    var _d = {name: _name, message: _message};
    var _list = {dialog.object}.getControl('listMessages');
    //create message as a JSON string
    var obj = {type: "messageBoard", name: _name, messageText: _message};
    //reset the message text to blank
    return JSON.stringify(obj);
    And the following code is in the client-side "webSocketOnMessage" event trigger, again with the additional alert to show what was received::

    if(e.message != '') {
    	var p = JSON.parse(e.message);
    	if(p.type = 'messageboard') {
    	var _d = [{name:, message: p.messageText}];
    	var lObj = {dialog.object}.getControl('listMessages');
    After launching a live preview, and a browser preview (launching each using "Full Preview"), and then attempting to send a message from one browser, or the other, using "Test Message 1" as the message, and "User 1" as the user name, the additional alerts show the following:

    The extra alert in the SENDING browser shows: {"type":"messageBoard","name":"User 1","messageText":"Test Message 1"}

    The extra alert in the RECEIVING browser shows:{"type":"messageBoard","name":"User 1","messageText":"Test Message 1","_sequence":9,"_id":"55900C9B-43AD-4C96-9F8D-E8C2E2C83020"}, after which the RECEIVING browser presents its own alert showing: "Received a message that was not in correct format. Messages must be JSON strings"

    It looks like the message is being broadcast, and received by the listening browser instances, but as soon as the client-side event "webSocketOnMessage" fires and tries to parse the message received, it complains about JSON formatting at "var p = JSON.parse(e.message)" because it can't parse the string as JSON string data, even though I used "JSON.stringify(obj)" in the return statement of the button click event.

    This seems like a simple, straight-forward example. What am I overlooking?

    Thanks in advance!

  • #2
    Re: Difficulty replicating WebSockets demo...

    I got it to work.

    I don't know why, but to make the JSON.parse command work as the demo shows, I had to change it from "var p = JSON.parse(e.message);" to "var p = JSON.parse(JSON.stringify(e.message));", even though the button click event has the command "return JSON.stringify(obj);" in its JavaScript event handler return statement.


    • #3
      Re: Difficulty replicating WebSockets demo...

      Man - thanks for posting this - it was driving me nuts. - Good solve.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)


      • #4
        Re: Difficulty replicating WebSockets demo...

        "var p = JSON.parse(JSON.stringify(e.message));"
        while you have solved the problem, i am just curious.
        in the above statement it seems that you are converting the e.message ( appears to be an object) to a string using JSON.stringify() then back to an object with JSON.parse the result.
        can you not just use the e.message itself? like var p = e.message;
        i cannot test since i do not have version 12, i am just curious.
        thanks for reading


        version 11 3381 - 4096
        mysql backend
        1 914 924 5171


        • #5
          Re: Difficulty replicating WebSockets demo...

          Well, what it did was show me what was going on and that the issue was running before the message had it's full value from what I could see, anyhow all working now - thanks.
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)


          • #6
            Re: Difficulty replicating WebSockets demo...

            This post was a life saver.

            can you not just use the e.message itself? like var p = e.message;
            Gandhi this works!


            • #7
              Re: Difficulty replicating WebSockets demo...

              michael, it made me more curious so i watched the video.
              the first post from mark quotes the code from the video verbatim
              //create message as a JSON string
              var obj = {type: "messageBoard", name: _name, messageText: _message};
              the red coloring is mine.
              this is an error, selwyn created an object and gave a wrong information stating that he created a string. it should have said create a JSON object then all will be understandable. if you notice following that line he is sending an alert
              alert(JSON.stringify(obj)); // you cannot stringify a string .
              this has led everyone on a primrose path.
              then you will understand why the code did not need stringify the e.message, just parse it to an object, p, to get the elements.
              if this is corrected then no one will need to stringify a string that is already there. the concept went wrong from then on.
              this is how i see it.
              you can test it in a simple ux/dialog and you will see it is really an object that is created not a string.
              put a simple button
              and in the onclick event declare
              var obj = {name: "gandhi", age:66};
              you will see it is an obj.
              thanks for reading


              version 11 3381 - 4096
              mysql backend
              1 914 924 5171


              • #8
                Re: Difficulty replicating WebSockets demo...


                I agree and understand. In following new code we are often too focused on maintaining the syntax than following the logic.

                Anyone hitting this problem should search the message board so your explanation will put them on the correct path.