Last post Oct 19, 2015 05:12 AM by Andrii92
Oct 08, 2015 06:52 AM|Andrii92|LINK
files. So, the questions are:
1) Is it possible to manually delete this files from signalr folder on hub disconnection process
2) In a lot of SignalR examples (for example the ShootR game) I've found that only one hub file, named /signalr/hubs is created and in my case some numbers are added, like /signalr/hubs?_=1444298238373. Is it expected behavior, maybe I'm missing something?
P.S I know that SignalR is expected to stop connection automatically, but in my case manual stop-start is crucial, and it would be preferable to keep the signalr/hubs folder clean.
Thanks in advance!
Oct 15, 2015 04:54 AM|Andrii92|LINK
Still no answer, maybe I am missing something, or maybe some additional info is required? As I understood after some investigation this numbers in hub link /signalr/hubs?_=1444298238373 is a hub connection id. If I need to manually disconnect and
Oct 16, 2015 06:34 AM|gtscdsi|LINK
By using the latest version 2.2.0 of jquery signalR , I don't see the similar issue as you mentioned.
1) Please have a check with the jquery signalR library version you used and updated to the latest one.
2) stop/start hub connection will definitely create a new connection with a new ID, but the ID should be in the format like 708ef655-52b3-4c44-b98b-a9c93b691321 rather than 1444298238373
3) 1444298238373 looks like a time stamp which you can get in the explore console by typing (new Date()).getTime().
4) In the ShootR game and my own test demo, we use
to request for the hub file. Please check with the code to see how you make the request to get the hub file.
Hope my answer will be helpful to you.
Oct 16, 2015 10:55 AM|sheng1016|LINK
Totally agree with gtscdsi. I believe the extra parameter (?_=1444298238373) is the timestamp when the script is created and was added to prevent caching.
If the URL is generated by the page script dynamically, I am quite sure that it was caused by jQuery. You may check
http://bugs.jquery.com/ticket/4898 for details and the workaround is to enable jQuery ajax cache as below.
Oct 19, 2015 05:12 AM|Andrii92|LINK
You are right, that helped and the issue is gone. Thanks guys!