On 03/27/2012 08:07 PM, Scott Talbert wrote:
> On Thu, 22 Mar 2012, Phil Dibowitz wrote:
> 
>>>> Once I'm back I wanna cleanup all the warnings I introduce on this branch 
>>>> and
>>>> implement config dumping. My friend ender is working on porting congruity 
>>>> to
>>>> the new API. I'll do a release, and if it goes well, merge the branch back 
>>>> to
>>>> head...
>>>
>>> If you want, I can probably take a crack at implementing config dumping,
>>> at least for usbnet...
>>
>> That would be great, help is always appreciated!
> 
> Hmm, so I think I've got config dumping more or less working for usbnet. 
> However, I'm wondering...should a dumped config look exactly like a config 
> from the website?  As in, if I download an updated config from the 
> website, write it to the remote, and then dump the config back to a file, 
> should the two config dumps match?  Because I'm not seeing that to be the 
> case.  The config I'm dumping from the remote is about 16K whereas what 
> I'm getting from the website is about 9K.

I wouldn't expect the non-binary contents to be identical (for example, we
fake the XML for non-zwave remotes), but the binary parts should be identical.
And I hate to ask the obvious, but are you comparing the compressed to
non-compressed files perhaps?

-- 
Phil Dibowitz                             p...@ipom.com
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Be who you are and say what you feel, because those who mind don't matter
 and those who matter don't mind."
 - Dr. Seuss


Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to