如何确保我的库支持 upnp 1.1
我有一个 upnp 库。正在使其作为受控设备工作。它可以与 UPNP 1.0 标准正常工作。我如何确保它也能正常处理 UPNP 1.1 控制点/控制设备请求 。 图书馆没有文档:( 我在源代码中搜索了新标头如 BOOTID 等。在代码中找不到新标头（根据 1.1）。 有什么方法可以确保我的解决方案也适用于 1.0 和 1.1。
问候 瓦伦吉斯
I have an upnp library .Am making it to work as a controlled device.It works fine with UPNP 1.0 standard.How will I make sure that it will gracefully handle UPNP 1.1 controlpoint/control device request as well.
There is no doccumentation for library :(
I searched in the source code for new headers like BOOTID etc .No new headers(according to 1.1) are found in the code ..
Is there any way to make sure that my solution will work with 1.0 and 1.1 as well.
Regards
Varunjith
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
v1.1 向后兼容 v1.0，因此任何表现良好的控制点都应该在您的 v1.0 设备上完美运行。
再想一想，我不确定 v1.1 是否包含任何额外的控制点功能。虽然写得不好的控制点可能会假设设备消息中存在 v1.1 标头，但 v1.0 设备如此之多，任何此类有问题的控制点都会很快被注意到并修复。
这是一种迂回的说法，我认为您已经可以确信您的解决方案将适用于 v1.1。
v1.1 is backward compatible with v1.0 so any well behaved control point should work perfectly well against your v1.0 device.
Thinking about it more, I'm not sure v1.1 even contains any additional control point features. While it would be possible for a badly written control point to assume the presence of v1.1 headers in device messages, there are so many v1.0 devices out there that any such buggy control point would be quickly noticed and fixed.
Which is all a roundabout way of saying that I think you can already be confident your solution will work with v1.1.