Results 1 to 10 of 21

Hybrid View

  1. #1
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    716
    Hi Paolo,

    I confirm that the upgrade to the new client library would be the best solution, however, is still valid the fact that the old version should work just fine, without any modification, with a 6.0.x server.

    That said, some considerations on your recent efforts:

    - in the LS subfolder you should add all the files of the client lib, not only the .js ones, and especially .html also.
    - Yes, I confirm that lightstreamer.js is the file of the new library (since Lightstreamer JavaScript client library 6) in client lib 5 (and earlier) that file is not needed.
    - In the version copied from production, you should check especially the misc.js file pointed by the page, and within that file, code lines like these:

    Code:
          lsEngine.connection.setLSHost("http://localhost"); 	// (set the hostname when deploying on WEB SERVER)
          lsEngine.connection.setLSPort("8080"); 			// (set the port when deploying on WEB SERVER)
          lsEngine.connection.setAdapterName("DEMO");	// the name of the Adapter Set
    that allow you to target the right server.

    Regards,
    Giuseppe

  2. #2
    Member
    Join Date
    May 2010
    Location
    Milano
    Posts
    14
    Quote Originally Posted by giuseppe.corti View Post
    Hi Paolo,

    I confirm that the upgrade to the new client library would be the best solution, however, is still valid the fact that the old version should work just fine, without any modification, with a 6.0.x server.

    That said, some considerations on your recent efforts:

    - in the LS subfolder you should add all the files of the client lib, not only the .js ones, and especially .html also.
    - Yes, I confirm that lightstreamer.js is the file of the new library (since Lightstreamer JavaScript client library 6) in client lib 5 (and earlier) that file is not needed.
    - In the version copied from production, you should check especially the misc.js file pointed by the page, and within that file, code lines like these:

    Code:
          lsEngine.connection.setLSHost("http://localhost"); 	// (set the hostname when deploying on WEB SERVER)
          lsEngine.connection.setLSPort("8080"); 			// (set the port when deploying on WEB SERVER)
          lsEngine.connection.setAdapterName("DEMO");	// the name of the Adapter Set
    that allow you to target the right server.

    Regards,
    Giuseppe
    Thank you Giuseppe, now also the old page, identical to the one in production, is working. I think there was a missing file also in the "pages" folder that I got from production. I wish to thank you especially for your patience!
    Best regards, Paolo

 

 

Similar Threads

  1. Replies: 4
    Last Post: April 8th, 2015, 02:55 PM
  2. Lighstreamer connection exception [iOS]
    By DrAma in forum Client SDKs
    Replies: 8
    Last Post: December 11th, 2014, 12:23 PM
  3. Replies: 13
    Last Post: November 27th, 2012, 09:14 AM
  4. Lighstreamer stress testing
    By Andrea in forum Adapter SDKs
    Replies: 3
    Last Post: April 30th, 2012, 04:39 PM
  5. Pull data from txt file to lighstreamer (NEWBIE)
    By forexinvestor in forum Adapter SDKs
    Replies: 1
    Last Post: December 23rd, 2008, 08:55 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 01:57 AM.