Well, I got it from module/owlib/src/include/parsedname.h:
/* ---- end Parsedname ----------------- */
#define CACHE_MASK ( (UINT) 0x00000001 )
#define CACHE_BIT 0
#define SHOULD_RETURN_BUS_LIST ( (UINT) 0x00000002 )
#define PERSISTENT_MASK ( (UINT) 0x00000004 )
#define PERSISTENT_BIT 2
#define ALIAS_REQUEST ( (UINT) 0x00000008 )
#define TEMPSCALE_MASK ( (UINT) 0x00FF0000 )
#define TEMPSCALE_BIT 16
#define DEVFORMAT_MASK ( (UINT) 0xFF000000 )
#define DEVFORMAT_BIT 24
But you are right -- I had just forgotten that the bits were documented on
the website. I'll fix the documentation.
Paul Alfille
On Tue, Apr 21, 2009 at 2:00 AM, Patrik Jansson <patrik.jans...@gmail.com>wrote:
> Paul,
>
> Thank you for the clarifications. So 256 should always be set no matter
> what, right? Then + 2 for bus list, + 4 for Persistence and +8 for alias?
> Shouldn't these be described on the flag word page? Well persistence is but
> not that 256 should be set and what 2 and 8 are for? Don't get me wrong
> here, I don't demand that such information is documented, I'm very much
> aware of the fact that this is an open source project and people are
> contributing on their spare time. Just trying to figure out if I could have
> got this information somewhere from the documentation or if I'm doing the
> right thing asking the mailing list.
>
> Patrik
>
> 2009/4/20 Paul Alfille <paul.alfi...@gmail.com>
>
> Hi Patrik,
>>
>> Thank you for your efforts.
>>
>> Actually, the bits should be:
>> 2 return bus list, (so the uncached, settings, statistics entries are
>> created by owserver, since ownet programs don't actually have the smarts to
>> add those entries).
>> 4 Persistance (if you wish, certainly a performance enhancement but not
>> used for 1-time programs like the owshell programs).
>> 8 Alias substitution (this is new, but owserver will use the alias file to
>> substitute human-readable names for known slaves)
>> 256 -- beats me why this is always included, and I wrote the program. But
>> we have plenty of bits and we aren't going to change old behavior.
>>
>> so 256+8+4+2=270
>>
>> ownet.c and ownet.pm (perl) do this. The other programs I didn't write
>> and can't vouch that changing the code is safe, so I only added some
>> comments.
>>
>> Paul Alfille
>>
>> On Mon, Apr 20, 2009 at 4:13 PM, Patrik Jansson <patrik.jans...@gmail.com
>> > wrote:
>>
>>> Hi,
>>>
>>> I've been working on a Java interface for ownet for some time now. I
>>> recently found out that there actually exists such an interface already. And
>>> with all due respect, I feel the code is a bit messy having everything in
>>> just one class file. Therefore I will continue my work on the Java interface
>>> which also gives me some interesting insights in the owfs protocol.
>>>
>>> So, to my question. I've noticed that the existing java interface aswell
>>> as the php interface have the default flag values set to 258 (or 0x102). Why
>>> is that? I can't even see those digits being accounted for on the flags
>>> page: http://owfs.org/index.php?page=owserver-flag-word
>>>
>>> For example, the least significant digit should be set to 4 for
>>> persistence, otherwise 0. So why does it default to 2? What does that mean?
>>>
>>> Thanks,
>>>
>>> Patrik Jansson
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> Owfs-developers mailing list
>>> Owfs-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> Owfs-developers mailing list
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
