invokeAction: fills same role as oBIX actions/user commands
I didn't post any previous discussion on these ops, so these are really just prototypes to play with and to provide feedback. I also beefed up docs for watchSub/watchPoll based on various conversations with engineers implementing these APIs.
Json
I've added a new JSON chapter for the specifying how to encode Haystack data in the "application/json" MIME type. Based on our discussion, I went with simple and clean versus 100% full fidelity with Haystack type system.
Points
I've really beefed up the docs on points to include:
Looks good. Any ETA on getting nav and navId into nhaystack?
Cheers, Aaron Schuenemann
Jason BriggsWed 3 Apr 2013
Aaron.... We are working on that right now, we actually are in beta starting today on it. It's really pretty cool, and working good.
We will be contributing it to opensource, and version 1 at the haystackconnect show this year (haystackconnect.org).
We are also doing a training and a session on it, I'm hoping you guys love nHaystack. It makes getting data out of Niagara way better, and faster. I can't wait to see what other people add to it.
Aaron SchuenemannWed 3 Apr 2013
The timing couldn't be better. We are anxiously awaiting the new features. I love what you guys have done to nHaystack already and I think the nav tag is probably our missing piece. At the very least it'll satisfy the customer's need for a representation of a physical hierarchy.
How do I get in this beta?!?
Mike JarmyWed 3 Apr 2013
Aaron, I've sent you a copy of nhaystack version 0.9.1, check your email
Christian TremblayFri 5 Apr 2013
I'd like to see that beta version, please ! :)
Jason BriggsFri 5 Apr 2013
Christian.... Send us an email, and we will see what we can do. :}
Brian Frank Mon 1 Apr 2013
I've posted a bunch of new documentation based on many of the forum discussion topics from the past few months. Here is biggies:
New REST Ops
I've added standard new operations to the REST protocol:
I didn't post any previous discussion on these ops, so these are really just prototypes to play with and to provide feedback. I also beefed up docs for watchSub/watchPoll based on various conversations with engineers implementing these APIs.
Json
I've added a new JSON chapter for the specifying how to encode Haystack data in the "application/json" MIME type. Based on our discussion, I went with simple and clean versus 100% full fidelity with Haystack type system.
Points
I've really beefed up the docs on points to include:
Didn't really get great resolution on historized tags, so better ideas welcome.
See Structure | Points
Coord
I added a new tag value type for coordinates per discussion 66
Change Log
Aaron Schuenemann Wed 3 Apr 2013
Brian,
Looks good. Any ETA on getting nav and navId into nhaystack?
Cheers, Aaron Schuenemann
Jason Briggs Wed 3 Apr 2013
Aaron.... We are working on that right now, we actually are in beta starting today on it. It's really pretty cool, and working good.
We will be contributing it to opensource, and version 1 at the haystackconnect show this year (haystackconnect.org).
We are also doing a training and a session on it, I'm hoping you guys love nHaystack. It makes getting data out of Niagara way better, and faster. I can't wait to see what other people add to it.
Aaron Schuenemann Wed 3 Apr 2013
The timing couldn't be better. We are anxiously awaiting the new features. I love what you guys have done to nHaystack already and I think the nav tag is probably our missing piece. At the very least it'll satisfy the customer's need for a representation of a physical hierarchy.
How do I get in this beta?!?
Mike Jarmy Wed 3 Apr 2013
Aaron, I've sent you a copy of nhaystack version 0.9.1, check your email
Christian Tremblay Fri 5 Apr 2013
I'd like to see that beta version, please ! :)
Jason Briggs Fri 5 Apr 2013
Christian.... Send us an email, and we will see what we can do. :}