Am 27.07.2016 um 22:02 schrieb Mick Sulley:
> Thanks for the suggestion Johan. I had a quick look and this seems to
> create a Python binding for owfs rather than owshell. Is that correct?
> In his mail 24/7/2016 Jan Kandziora <j...@gmx.de> explained that owshell
> is a better way to access the system than owfs, do these same
> limitations apply to pyownet?
>
I think I have to clarify the confusion.
Our whole toolbox is called OWFS. This includes owfs/fuse, owserver,
owshell, and the various language bindings included. It's called OWFS
because owfs/fuse was first. "ABC bindings for owfs" doesn't mean the
bindings are going to use the fuse interface (with its serious limitations).
The language bindings included in the OWFS toolbox either use OWlib, the
underlying driver library, directly. This enables you to create
stand-alone binaries without an owserver running. But owlib also *MAY*
use owserver. Owlib can do it all.
Or they use the owserver protocol, either through the general OWnet API
(the owshell tools do it that way) or through a homebrewn solution. It's
socket communication and the protocol is simple enough to do it all on
your own. You need to run an owserver to use this method.
The language bindings outside the OWFS toolbox all use the owserver
protocol, as far as I know.
The recommended method to use owfs is through owserver. It gives you a
good abstraction of the driver, much better than using OWlib directly.
Kind regards
Jan
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
