[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
Re: [Project] Kbd/LCD device
- To: ukha_d@xxxxxxx
- Subject: Re: [Project] Kbd/LCD device
- From: patrickl@xxxxxxx
- Date: Mon, 04 Jun 2001 20:00:38 -0000
- Delivered-to: rich@xxxxxxx
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
--- In ukha_d@y..., "Steve Morgan" <steve@s...> wrote:
> Sorry, Ant, but I think this is bollocks!
>
> ;-) <--- deliberately inserted cheesy grin
>
> There's absolutely nothing to stop a 'server' initiating a
connection to a
> 'client' device, it's just that the 'client' needs to be able to
accept a
> HTTP connection.
So if you put a web server on both ends of the relationship, you can
do push. That's a rather unusual way of looking at things.
A (not very good) analogy would be if, in order to download a file,
you first had to install a full blown ftp server on the device you
wanted to download the file onto.
Either way, you have to remember that we are dealing with devices
with very limited capabilities in terms of processing power and
storage. I can't see a tangible benefit from forcing these devices to
talk a cut down version of http. With the exception of the console,
these devices will only be talking with other embedded devices. And
if the console has to support some reciprocal server arrangement,
it's going to be a piece of bespoke software anyway.
SOAP sounds interesting. Anyone want to provide a definitive URL?
Patrick
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Home |
Main Index |
Thread Index
|