Fine with me! We'll stick with strict binary. That scenario, the owserver <-> owserver ,-> owserver ... comes up in other contexts, like temperature conversion, caching, etc.
For caching, the cache is done at the final level, when the actual physical bus master is accessed. For temperature scale, the conversion is done at the top level, (except for ownet clients like owread, where it's done at the the top owserver level). For aliases, it's even more complex (and not yet perfect based on the bug reports). Paul Alfille On Fri, Jan 28, 2011 at 3:58 PM, Roberto Spadim <[email protected]> wrote: > i use mysql for many years, when they changed from latin1 to utf-8 > (between mysql 3 to 4 or 4 to 5) i had many problems since mysqldump > start using utf-8, after many time i get the information how stuff > works and today i know how to use it > i think that untranslated (unsigned char (binary)) is better than > (character (text)) since owfs make comunication over a binary protocol > (onewire) and over a binary lcd protocol > translation could be implemented before owfs > for example let´s think about a owserver - owserver - owserver - > onewire - display layout > if we put the first owserver to use translations and second to use > other translation and third.... we will get really crazy > i think that a tranlation on owclient could be really easier to implement > ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
