Thank you! I'll try it as soon as I can.
/på
2011/6/23 Paul Alfille
> Hi Patrik,
>
> Thanks for finding this problem. It's been fixed and will be part of
> the next release.
>
> Basically you found 2 problems:
>
> 1. We need to handle structure/1F/aux as a file, and
> 1F.123412341234/aux as a d
Hi Patrik,
Thanks for finding this problem. It's been fixed and will be part of
the next release.
Basically you found 2 problems:
1. We need to handle structure/1F/aux as a file, and
1F.123412341234/aux as a directory.
2. We were too lenient with filenames.
10.12341234/id# is a file
I'm still having difficulties with structure.
For example, I would expect /opt/owfs/bin/owread -s
192.168.1.10:3001/structure/1F/main to return proper response saying
this is a directory
instead of: ServerRead: Data error on /structure/1F/main
And I would expect /opt/owfs/bin/owpresent -s
192.168
I'm running 2.7p35 and owdir /structure/ does not list my alias. And
owdir /structure/MyAlias/ shows nothing. Furthermore owread
/structure/MyAlias/family gives:
ServerRead: Data error on /structure/MyAlias/family
Was the support for using alias name in structure path added after
2.7p35 perhaps?
The next release will improve alias handling.
Nevertheless, alias_name->family should give family code.
/structure/(alias_name/family)/...
In general you can get data about an alias' unique code by using the properties:
# first byte
alias_name/family
# middle 6 bytes
alias_name/id
# last byte
Hi,
I'm looking to update the jowfsclient library with both fixes and new
features. But I just ran into some problems.
My user story is pretty much this: I want a generic way of reading the
structure information from any type of address (including aliases).
So, for example:
Given /10.AC8CB611080
