I've just posted Build 1.1.4 of NHaystack to BitBucket.
This build changes the way that Refs are reported when HTTP requests are made from outside the station. Its an important change, so anyone who uses siteRef and equipRef over port 80 should adopt this new build.
In previous builds, the id for each rec is generated such that the Site-Equip-Point hierarchy (if there is one) is obvious just from looking at the id itself. For instance, here is an id for an equip:
S.MySite.MyAHU
ids are still generated this way in 1.1.4. However, there was a bug in previous builds that caused the equipRef for any points that exist underneath an equip to be reported externally as a slotPath-style Ref, e.g.
C.some.slotPath.to.MyAHU
The same problem existed for siteRefs. Build 1.1.4 fixes this problem so that Refs are always reported externally as Site-Equip-Point Refs (if there is a hierarchy built). This way the equipRefs and siteRefs actually match the ids for the record that the Ref is pointing to.
Several people have told me about this problem, and I know that there is production code out there in the user community which works around this issue. I am cautiously optimistic that this build will not break any existing code, but if it does, please contact me and I'll help you figure out what you need to do.
Technical Note: Internally, nhaystack still persists the zinc for each Ref as a slotPath-style Ref, never a Site-Equip-Point Ref. It works this way to make nhaystack run more quickly while building the internal cache.
Mike Jarmy Thu 17 Apr 2014
I've just posted Build 1.1.4 of NHaystack to BitBucket.
This build changes the way that Refs are reported when HTTP requests are made from outside the station. Its an important change, so anyone who uses
siteRefandequipRefover port 80 should adopt this new build.In previous builds, the
idfor each rec is generated such that the Site-Equip-Point hierarchy (if there is one) is obvious just from looking at theiditself. For instance, here is anidfor anequip:idsare still generated this way in 1.1.4. However, there was a bug in previous builds that caused theequipReffor any points that exist underneath anequipto be reported externally as a slotPath-style Ref, e.g.The same problem existed for
siteRefs. Build 1.1.4 fixes this problem so that Refs are always reported externally as Site-Equip-Point Refs (if there is a hierarchy built). This way theequipRefsandsiteRefsactually match theidsfor the record that the Ref is pointing to.Several people have told me about this problem, and I know that there is production code out there in the user community which works around this issue. I am cautiously optimistic that this build will not break any existing code, but if it does, please contact me and I'll help you figure out what you need to do.
Technical Note: Internally, nhaystack still persists the zinc for each Ref as a slotPath-style Ref, never a Site-Equip-Point Ref. It works this way to make nhaystack run more quickly while building the internal cache.