On 5 Dec 2006 at 14:30, Paul Alfille wrote: > A volunteer! To help with specification and testing.
heh > > I propose we start with owrest and then decide if it's function should be > folded into owserver. but I am confused. REST is just a symantic for how to use HTTP verbs. So, why have a distinct owhttpd.. Wouldn't this just be an improvement to the existing owhttpd? And why would this go into owserver? Isn't that breaking the layering? > > So: > 1. What is the format of the returned object? That depends on the noun and the verb.. ;-) But seriously, what kinds of ibutton objects should return a list of other objects? an adapter.. a switch? I'm not familiar enough. REST says that a GET on a "collection" returns a list of 'child objects'. But a switch could return a list of addresses on either branch of the switch, OR it could also return information about the switch itself, right? > 3. Do you want XML or JSON? If XML, can you mock up some return values? I could prototype a nice REST server in python, if you get that pure python interface working. ;-) > Actually that would be the most useful. Can you mock up some messages for > each of the returns: directory, property and "setting a property" I'm willing to work on this, but I need to know more about the different types of 1 button devices and stuff. I'll need to look at the owfs website some more.. -- Brad Clements, [EMAIL PROTECTED] (315)268-1000 http://www.murkworks.com AOL-IM or SKYPE: BKClements ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
