Hi Folks, I searched for Onvif discussion / development formums and maybe just the pay for development forum exists at onvif.org / developeronvif.org? Any suggestions on best free place to discuss implimenting the client side of this spec?
I work for a large company doing retail home based video functionality and we have a problem that would be solved, if our application tell the camera the client URL that a stream (code, frame rate, bit rate) should be opened to. IE the client opens a port and we need the camera to make the socket to the client.
Today we have the worst possible situation, our application has to proxy every stream byte, causing proxy CPU load as well as SSL load on our app box in the home. All would go away if the camera could create the socket direct to the client. Is this supported within ONVIF?
Thanks, curt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Folks, I searched for Onvif discussion / development formums and maybe just the pay for development forum exists at onvif.org / developeronvif.org? Any suggestions on best free place to discuss implimenting the client side of this spec?
I work for a large company doing retail home based video functionality and we have a problem that would be solved, if our application tell the camera the client URL that a stream (code, frame rate, bit rate) should be opened to. IE the client opens a port and we need the camera to make the socket to the client.
Today we have the worst possible situation, our application has to proxy every stream byte, causing proxy CPU load as well as SSL load on our app box in the home. All would go away if the camera could create the socket direct to the client. Is this supported within ONVIF?
Thanks, curt