-
March 12th, 2014, 04:48 PM
#1
OK - so assuming I don't want to impact all the difference browsers connecting to the server, I need to use option 2 and condition the code based on the browser type?
-
March 13th, 2014, 08:46 AM
#2
Yes, you are right.
Option 1 is practicable if you could reserve a Lightstreamer test server to find out the Safari issue.
Nevertheless, please note that you may define a special case recognized by the user-agent supplied with the request in order to differentiate the behavior of the server. Please refer to the inline documentation of the <special_case> parameter.
-
March 20th, 2014, 04:01 PM
#3
I have just noticed that even without the javascript change, Safari is using HTTP-POLLING anyway. So I don't think that forcing it to use polling is going to fix my problem.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 01:14 PM.
Bookmarks