Changes

Jump to: navigation, search

XMPPHWFS

376 bytes added, 07:11, 12 January 2012
modification after corecore's PUBSUB suggestion
Under the barbarian name of XMPPHWFS stands the following idea:
'''hardware IOs made available ''' (on a fuse filesystem ) '''through xml xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change a bit. ''locmon2'' seems like a good candidate to me.
XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and imagine doing stuff likeimpractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.
garage_temp = myHome/garage/temperature garage_heat = myHome/heating/pump1 if (( $garage_temp < 2 )) then echo 1 > $garage_heat fi[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]
the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
* The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
* GUI can also be implementd as a bot. Simple and clean.
* Debugging new hardware is simply done through communication with a human client.
 * ''corecode'' suggest to use the [[Imagehttp:Xmpphwfs arch//xmpp.svg|thumb|XMPPHWFS architecture]org/extensions/xep-0060.html PubSub] XMPPHWFS is meant to replace [http://davidjabber.lutolf.netorg/dtprotocols/locmon locmonpubsub mechanism]for event notification, which in my opinion was I think he's bloody right on this.* GUI can also be implemented as a bot (ctrl_bot?). Simple and clean. Use a of cache DB is a good idea but to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax. Help is too buggy needed here.* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG graphs] and impracticalupdate the cache database on the same occasion. from a recent copy MRTG config can of ''20 minutes'', it seems course be generated automatically and graphs included in the industry is also heading towards something alikeGUI.* The Fuse inteface, only for home robots and social networkingif needed, should also be implemented as a bot. WTFSimply specify where to mount the filesystem, tell me why connect your vacuum cleaner should tell all your facebook friends therebot, you's re done. No need to have a plant in its waymodified jabberd. Any interface of this type should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.
it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.
Petaflot
77
edits
Retrieved from "http://fixme.ch/wiki/Special:MobileDiff/1428"