I am working on an OCF bridging project (OCF 1.0 to non-OCF devices) on the 1.3-rel branch and am experiencing some issues and would like some input.
Our core application has many virtual resources and also loads bridging plugins which essentially have their own instance of the stack. I expected devices discovered and added via the mini plugin manager framework would appear in the /oic/res provided by the 'main' stack instance, but they do not. I then assumed I might need to enable ROUTING_GATEWAY in my project. When I enabled this build flag I found that my core (non-plugin) code could no longer observe my own virtual resources because the routing manager aborts the observe request with a "Packet is of its own" message. Am I missing something? Do I need to handle adding the bridged devices to the main stack instance's /oic/res myself? How does gateway routing figure into this configuration, or is that only required for routing to devices running in OCF stacks outside of the main instance and those of the mini plugin instances? Thanks, Thomas Lea Xfinity Home Comcast
