From: Steve K. <st...@ka...> - 2005-01-08 18:14:19
|
Hi Coleman, >>Okay. I suppose that we need to think about making the rest of the code >>thread safe, which it currently is not (i.e. globals and function static >>variables). > > I already did some of that. My code is so different from what's in Sourcesafe > that I should probably create another dev tree. How would I do that? Well, you did it once with the MS/TP checkin ;-) Perhaps just use CVS and import the new project. bacnet-mt or something. Perhaps someday we can collaborate on the work and the core files, but until then multiple projects might be the way to go. I would be interested in seeing your router code someday. Did you see the new project that Joel created on SourceForge for routing? http://sourceforge.net/projects/bfr/ > You hit the nail on the head (as always). Tags sound like the way to go. > > However, my level of confusion grows exponentially when I start trying to > understand tags as they're described in the BACnet spec. Can you (or is > there a tutorial or something) help be better understand them? bacdcode.c has some information about data type tags, but it all came from the BACnet Standard, clause 20, Encoding BACnet Protocol Data Units. When trying to figure out how to encode or decode a message, that is the clause that I go to. There is another document, "Understanding BACnet Encoding," on the BACnet.org site that talks about tags and other low level details: ftp://ftp.bacnet.org/Encoding.doc Best Regards, Steve PS: I am sending this along to the developers list. -- http://kargs.net/ |