Been using nHaystack for quite a while, it's great for exposing any kind of object that makes it into Tridium's data model.
What about going the other way? Suppose I wanted to bring in a bunch of third party devices into my jace, and the only API they exposed was Haystack? Has anyone ever thought about making a driver to go from Haystack to a Tridium model? That way we could use the jace as a staging point for everything. Basically instead of a Haystack server, the driver would act as the client.
Anyone thought about this? :)
Brian FrankThu 19 Dec 2013
It has definitely been thought of :) It would be a HaystackNetwork that fits into Niagara's existing driver model.
Aaron Schuenemann Tue 17 Dec 2013
Been using nHaystack for quite a while, it's great for exposing any kind of object that makes it into Tridium's data model.
What about going the other way? Suppose I wanted to bring in a bunch of third party devices into my jace, and the only API they exposed was Haystack? Has anyone ever thought about making a driver to go from Haystack to a Tridium model? That way we could use the jace as a staging point for everything. Basically instead of a Haystack server, the driver would act as the client.
Anyone thought about this? :)
Brian Frank Thu 19 Dec 2013
It has definitely been thought of :) It would be a HaystackNetwork that fits into Niagara's existing driver model.