Any IP Camera owner can optionally easily get and use
All my many different IP Camera examples bundled together with one hour of one-on-one support to implement them. Save Time and Money
Click Here!Here are some more details on some of the features of this Interface which have not been explained in much detail before.
Different Ways This Interface Can Be Configured To Operate
Browser (HTTP) <-> Interface <-> IP Camera (HTTP)
Browser (HTTP) <-> Interface <-> IP Camera (HTTPS)
Browser (HTTPS) <-> Interface <-> IP Camera (HTTPS)
Browser (HTTPS) <-> Interface <-> IP Camera (HTTP)
The above allows you to configure the flow end-to-end, on a per camera basis on how IP Camera controls will be used and/or how images will be pulled from IP Cameras. It also allows you to control and display IP Cameras which don't natively support HTTPS access methods in web pages which are using HTTPS vs. HTTP. For both private and public use.
Regardless of what methods are used above. At no time does any information about a IP Camera travel over the Internet from/to the Interface to any devices browser about a IP Cameras DDNS, ISP IP Address, Port or User credentials.
The Interface also supports using a optional unique logon and password, to access IP Cameras. Even if the IP Camera itself, does not support HTTPS access methods. This allows you to more securely use those logon credentials to access that or those IP Cameras. Without having those logon credentials being "in the clear" as they would normally be when using HTTP access methods.
For public use. Because the Interface has a configuration option to store the last image from the IP Camera received to disk. It allows one to configure pulling that image from disk vs. going to the IP Camera each time for a fresh image. Based on how old that image on disk is. Before grabbing a fresh image from the IP Camera. Which is a configuration option in the Interface. There is no file clutter to do this. Since only the last image received from the IP Camera is stored on disk and the same image file on disk, is reused when newer images are received from the IP Camera are saved.
As an example. Say you had 100+ website visitors simultaneously viewing a web page that the Interface was used in and that web page was automatically refreshing IP Camera images once a second, in that web page. If you configure the Interface to get the IP Cameras image from disk if that image on disk is one second old or less. Then, only one website visitor would cause a fresh image to be pulled from the IP Camera. The others would automatically be pulling the image from disk for those IP Cameras instead. If that image was one second old or less. When those others made their new image request for that IP Camera. This allows you to throttle real-time requests to IP Cameras, automatically. For public use.
Since the Interface allows IP Camera images to be resized on a per IP Camera basis. It allows you to display as many IP Camera images at the same time at whatever resolutions you choose. For both private and public use. On a per IP Camera basis. Not being restricted with only using the actual size image provided by the IP Camera itself. You can create copies of the Interface that may be better suited for mobile devices. While another copy of the Interface controlling/displaying the same IP Cameras would use larger IP Camera image resolutions. For other devices. With or without any custom text and/or logos/images you merged with the IP Cameras original images.
For private use. Because the Interface is compatible with all Internet browser capable devices. It allows you to instantly check on the health and status of many IP cameras at the same time. From virtually any Internet browser capable device. Without any need to first install any other software first, on any device. While also allowing using secure access methods to be used, even if the IP Cameras themselves don't support secure access methods. While also controlling bandwidth usage while doing so, if needed.
With security vulnerability abuses increasing daily. It's never a good idea to ever expose publicly or privately over insecure Internet connections. The DDNS or ISP IP Address, Port or user credentials of any IP Camera. When/If that can be avoided. Which this Interface can do and does for both private and public access to your IP Cameras. To do otherwise. Is truly inviting trouble, with open arms.
For the download link to this Interface and many live demonstrations using this Interfaces features using live IP cameras. Please go here:
http://www.openipcam.com/forum/index.php/topic,963.0.htmlDon