{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/f7ba93795ded4028ed12604d484e390c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"f7ba93795ded4028ed12604d484e390c","url":"https://api.github.com/users/barberdt","login":"barberdt","id":918406},"milestone":{"state":"open","open_issues":7,"url":"https://api.github.com/repos/buglabs/bugswarm-connector/milestones/3","due_on":null,"description":"The initial release of bugswarm-connector and the web management interface.  As discussed in irc meeting on 10/4/11, connector will not be apart of the oct 11th DP release.","number":3,"title":"connector/webui initial release","creator":{"avatar_url":"https://secure.gravatar.com/avatar/c72aeb67cdbd5893a996ffbcdfaded17?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"c72aeb67cdbd5893a996ffbcdfaded17","url":"https://api.github.com/users/kgilmer","login":"kgilmer","id":49683},"closed_issues":1,"created_at":"2011-10-04T22:47:19Z"},"assignee":{"avatar_url":"https://secure.gravatar.com/avatar/c72aeb67cdbd5893a996ffbcdfaded17?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"c72aeb67cdbd5893a996ffbcdfaded17","url":"https://api.github.com/users/kgilmer","login":"kgilmer","id":49683},"updated_at":"2011-10-27T11:29:18Z","labels":[],"closed_at":null,"comments":13,"url":"https://api.github.com/repos/buglabs/bugswarm-connector/issues/20","body":"Hey Ken,\r\n\r\nSo I was chatting with aturls and camilo about connector's current status and how that will fit in with santiago's management UI, and we determined that there is a disconnect between the capabilities feeds that connector is producing (i.e. LCD, GPS, Acceleration, etc...) and the expected functionality.  The way they explained it was that these feeds will not only contain the meta-information regarding the capability (i.e. whether there is a GPS fix or not, whether the antenna is active or not), but they will also contain the valuable information from those capabilities (i.e. the actual LatLon data from the GPS module, the actual acceleration data). This is so that the management UI will be able to query a standard set of feeds (those announced as device capabilities) and present the returned information to the user. \r\n\r\nFor instance, right now, I am using an app (http://pastebin.com/AGKTVz9w) to grab the LatLon data from the IPositionProvider and push it to swarm. aturls and camilo are suggesting that this type of information would be included in the GPSX (where X is the slot # of the module) feed that is produced by connector. \r\n\r\n**Note: If the GPS module cannot get a fix, the IPositionProvider will currently return an NPE when trying to get the GPS data, so this may break that feed if the above is implemented. I'm not sure what kind of workarounds there are for this, but hopefully we can make it work. \r\n\r\nI know this is a lot and may be confusing, so please let me know if you have any questions. This was news to me as well, but I guess it makes sense when you think about the management UI that santiago is working on needing a standard set of feeds where it can get actual GPS, Acceleration, and other data 'stock' data from.\r\n\r\n-Davis\r\n\r\nP.S. Here is what the announced feeds currently look like when LCD and GPS modules are plugged in.\r\nhttp://pastebin.com/F7xLSY6N\r\n\r\nP.P.S. i just got the bright idea to format jumbles of JSON before I paste them to you, so if you need me to do that with something I already pasted just let me know.\r\n","html_url":"https://github.com/buglabs/bugswarm-connector/issues/20","number":20,"title":"Capabilities feeds and their expected functionality","id":1768862,"created_at":"2011-09-28T21:30:05Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/69ac64868a0f2d5fee53cad900bf7fc5?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"69ac64868a0f2d5fee53cad900bf7fc5","url":"https://api.github.com/users/aturley","login":"aturley","id":714337},"updated_at":"2011-10-27T11:29:18Z","url":"https://api.github.com/repos/buglabs/bugswarm-connector/issues/comments/2542336","body":"@kgilmer feeds are part of a contract between the Connector and anything that wants to cooperate with it, which for right now means the web UI. From the Connector's point of view, nothing should have changed with the removal of the feed API, it just means that now the web UI (or the test code) has to assemble the appropriate message to send to the Connector instead of relying on the BUGswarm server to put the message together and send it.\r\n\r\nAnd yes, you are correct, the method call in part B is part of the now deprecated feed API. So whatever message the BUGswarm server had been generating based on that call now needs to be created by the client code and sent using the streaming API (or directly through XMPP while that channel is still available).","id":2542336,"created_at":"2011-10-27T11:29:18Z"}}