Re: http://cvs.sourceforge.net/viewcvs.py/xanadux/qomunicator/

[Luke Kenneth Casson Leighton]

On Mon, Jan 16, 2006 at 11:32:14PM +0100, Pawel Kot wrote:
> Hi,
> 
> On 1/16/06, Luke Kenneth Casson Leighton <address@hidden> wrote:
> > On Mon, Jan 16, 2006 at 11:05:52PM +0100, Pawel Kot wrote:
> >
> > > > Daemon that presents 5 virtual telephones talking to one real
> > > > telephone, or something like that. Similar to gpsd.
> > >
> > > Need to look at gpsd. But I think virtual telephone may be a bit too
> > > much. I like to look at it as on the message bus supporting
> > > synchronous and asynchronous communication. I can't see any additional
> > > value from virtual phone abstraction.
> >
> >  the principle behind gpsd is that you issue _simple_ commands
> >  of one character in length, and the responses come back "preparsed".
> >
> >  so gpsd takes care of parsing the NMEA data for you, and if you happen
> >  to know which one-character commands to type, then you can just telnet
> >  to gpsd and get a rough idea of what's going on.
> 
> But that's just proxy. Just a bit more intelligent. 

 yes.

 not sure if there's a significant difference between a proxy and the
 multiplexing daemon concept.

> No need for any
> virtual phones (if we have the same understanding of the virtual
> phone). Just the API for giving commands and sending responses. State
> and other internals are handled internally by the proxy. And I think
> AT command interface will not be suitable: 

 no, not at all.

> you won't be able to do too
> many things (starting with file operations).

 ack!!