Re: [LHA-misc] Line parsing routine

[Neil C. <nc...@ho...>]

Paul Fox wrote:
> 
>  > to note that if we needed compression on the fly that the file size
>  > would hinder things. Because of my networking background I tend to think
>  > that compression is best left to storage. If we compress data over a
> 
> in general you're right -- but if the data is, say, the memory image
> of the device in question, then it clearly can't be stored compressed.
> and equally clearly, it could be quite large -- so if you wanted to
> request a full memory dump of your 32KB refrigerator controller, you
> might want the ability to do on-the-fly compression.  another example
> might be wanting to speed up the download of a large background image
> to a dedicated controller -- perhaps for the touchscreen on that same
> refrigerator.  :-)

The internet 'frig is coming, the internet 'frig is coming .... :-)

You make a very good point and with the recommendation that Jay made (S Records)
it's still possible to create a mode where the data sent is compressed and
sent as a line of X characters with addressing and CRC. This is of course an
extended mode. So there is a possible solution to a problem I hadn't thought
of.
 
> but clearly compression is at odds with ascii data representation.  i say
> do the simple things first, and leave the hooks in the protocol so you
> can add what's necessary later.  (e.g. perhaps an optional "encoding=foo"
> parameter.)

Simple for now but we can extend as necessary. Leaving the option open
is always a wise idea. We may never use it but we also haven't locked
ourselves into anything too restrictive.

Now where the heck to docuemnt this!

-- 
Linux Home Automation           Neil Cherry             nc...@ho...
http://members.home.net/ncherry                         (Text only)
http://meltingpot.fortunecity.com/lightsey/52           (Graphics)
http://linuxha.sourceforge.net/				(SourceForge)