Re: [LHA-misc] Line parsing routine
Status: Beta
Brought to you by:
ncherry
From: Neil C. <nc...@ho...> - 2000-11-28 05:13:48
|
I've looked over what you've posted so far and it looks good. Now I have few questions. >What I've got implemented as far as commands are: >USER <user id> >PASS <password> The login/password part is difficult, how does one let an LCD login? We can allow a default/guest id that is active when they connect. This would allow monitors to do their work. But logins would have to be through a secure channel (no plain text). That one we can leave for a while. >QUIT >HELP (displays allowed commands) >LANG (tells language variants - AGENT-1.0 MCUSTOM) I understand, yet I don't. >SET <> >GET <> SET X10:FF ON or SET addr=1:FF value=ON (should be case insensitive, yes?) >NOTIFY <> (Sets notification events to be received) I've been calling the monitor, I think NOTIFY is part of one protocols so the use notify is a good idea. >Mxxx <> (Module specific for "playing", dlding code/IR on ocelot Sort of a raw command, like !12000200. I'd like to see an example of this. >General format of addresses is: >[device name:]device.domain.point >[device name:]device.domain.group.point ad infinitum (SP?) I wonder can we drop the addr= and value= ? If they're always in the same position we can drop them. But if the addr= can be replaced with something else then we'll need them (is this too short sighted?). Also if it's device name can we drop the ':'? The x.y.z.aa.bb. .... should stay, that way we can grow if the devices begin to expand beyond what we've planed for. Also can we have more than 1 value? Say we d/l some code to the Ocelot, we can first send the size of the file (make reserving memory easier) then the actual file, which can we a stream of 8 bit characters (no null or <CR> to worry about or escape). -- 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) |