3 ms·
I've been in the ONVIF world. Neat standard, but most of it is never implemented. I ended up reverse engineering a bunch of the hikvision protocol for the bit
by fullstop 6y ago
I've been in the ONVIF world. Neat standard, but most of it is never implemented.
I ended up reverse engineering a bunch of the hikvision protocol for the bits that I could not do with ONVIF.
- ChrisMarshallNY 6y agoIt's a really klunky standard. It's based on SOAP/WSDL, so a lot of "modern" folks don't like it. That's not really too much of an issue in my driver. I just licensed SOAPEngine, and that layer is sorted. I think that one of the reasons that its uptake has been slow, is because manufacturers like to keep everything "in-house," and aren't too happy to allow devices they don't make to access their equipment. I understand that. I really do. I worked for a manufacturer like that for ages. All kinds of hell can break loose, when you move from proprietary to open. It's not a simple transition. The people that do like it, though, are the integrators. They are the ones that buy cameras in lots of a thousand, so there is definitely a case to be made in its favor.
- dekhn 6y agoeven old folks don't like SOAP or WSDL. They were turkeys when they were released, and now they're just old turkeys. (I developed pyGridware, which was based on SOAP and WSDL. It took hundreds of lines of code just to build Echo Hello World.
- ChrisMarshallNY 6y agoYup. I am quite grateful for SOAPEngine[0]. Even then, I had to do a bit of hackery (using the proper callbacks)[1], to make auth work properly. [0] https://github.com/priore/SOAPEngine https://github.com/priore/SOAPEngine [1] https://github.com/RiftValleySoftware/RVS_ONVIF/blob/master/RVS_ONVIF/src/RVS_ONVIF_Internals.swift#L505 https://github.com/RiftValleySoftware/RVS_ONVIF/blob/master/...