I have a application where I am doing recording through a third party device.Recording is started and stopped through a asp.net web service which uses the api of the recording device to start and stop the recording..
I am able to start and stop the recording through ajax in normal cases and the functiaanilty works fine in all browsers..
But,once accidently one user without stopping the video,closed the browser in which case the recording could not be stopped..and it went on recording...
So,please suggest me a way so that I can detect the time or anything that tells me when the browser is closed and then I can pass the off request to stop the recording..!!
I have read about WEB SOCKETS but they say this class is to be used in VS2012..So,I have not found any compatible solutions yet..
Related
We have embedded a Bot on a web page through the web chat channel, if the Bot is idle for 10 minutes or so and then a question is asked, the Bot does not respond to it, however when the same question is asked again immediately it responds as expected.
On investigating the network capture, we observed the response received when the question was asked for the first time was 500: Internal Server Error with message as "failed to send message"
Are you running the bot in Azure? If so, make sure you have "AlwaysOn" enabled; otherwise the web app will be unloaded if it's idle for a period of time. Check this for a similar problem.
Always On. By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. In Basic or Standard mode, you can enable Always On to keep the app loaded all the time. If your app runs continuous web jobs, you should enable Always On, or the web jobs may not run reliably.
You can read more about the web sites configuration here.
I need in autoresponder. I develop flash application and I need substitution flash file from server to my local debug flash.
I used Charles Proxy but in last week it became badly: internet connection very slow, some responses can't wait for request.
Is there a same solution for this micro task? May be little extension for browser? Or can anybody create this extension for chrome or safari?
Or Do you know why my Charles works slowly?
I'm using Firefox for a digital signage application, and there a couple of scenarios where a Server not found might result.
Network outage on boot
DNS fails to resolve for the homepage
Server (its homepage) fails to respond
Boots and the network just isn't ready by the time Firefox is loaded
Browser crashes, process is restarted, but the network is down
In such cases I would like to detect this state and simply kill and restart the process after a minute. Any other tweaks or suggestions, I'm all ears.
You do not need to consider the case whereby the loaded Web application loses Internet connectivity. That scenario I think has been handled by the Web app itself, once it has loaded.
I don't want to go down the local httpd or local extension/addon route.
Thank you in advance,
I've discovered a simple solution of overriding Firefox netError.xhtml to do a simple location.reload every ten seconds.
Source code can be found from https://github.com/Webconverger/iceweasel-webconverger/blob/master/content/netError.xhtml#L410
I am doing a simple bonjour broadcast using NSNetServices. Everything is working great when I start and stop the bonjour sharing at application launch/quit. However if I turn off bonjour using the stop method call, my app still appears to be broadcasting a dead service even after the netServiceDidStop: delegate message gets called, which prevents restarting of the service until after a relaunch of the app. Apple's documentation makes it look very straightforward, just publish or stop as needed... Am I missing something?
It seems that sometimes services are shown even when they are no longer available.
From Apple documentation:
Because failing to show a valid service is a bigger problem for the user than showing a stale service, Bonjour deliberately errs on the side of assuming that a service is still available.
.
.
although Bonjour generally discovers new services within a few
seconds, if a service goes away, the disappearance of the service may
not be discovered until your app tries to connect to it and gets no
response.
You should not assume that just because the Bonjour APIs report a
discovered service, the service is guaranteed to be available when the
software tries to access it.
Connecting to and Monitoring Network Services: When resolving fails
This should work if multiple windows are open.
My application is in J2EE.
I already tried some javascript like on window.unloadn but this kind of solution is not solid.
If you mean on the server side, the best way is to implement a heartbeat. If none of the windows from this webapp are open, nothing sends a heartbeat, and a server after some time will know the app is disconnected.
If you mean on the client side, there's no 100% reliable way, since the browser might die from external causes (kill/crash/reboot), but a timed-out cookie that is updated regularly in a heartbeat-like fashion might work
HTTP is a stateless, meaning you can't tell when a browser is closed.
Your attempt to use window.onunload does not always work because the browser could exit before executing your event handler.
The technology used to find out if a user has closed their browser (or a best guess) is to use timeouts. Sessions will automatically timeout (this is configurable) - in asp.net the default is 20 minutes. If there is no activity, the timeout kicks in.