> -----Original Message-----
> From: Adrian Pfisterer [mailto:[EMAIL PROTECTED]]
>
>
> With JetSend two communication appliances *negotiate*
> (through the JetSend
> protocols) content. And (this is the clincher) the two devices are
> required to support the JetSend mandatory content format.
> This guarantees
> that the two devices will be able to exchange content in a
> meaningful way.
>
> For example, a PalmOS device, specifically the DateBook
> application, wants
> to exchange an appointment with a WinCE device. The JetSend
> enabled PalmOS
> device opens a JetSend session with the WinCE device and
> essentially says
> "I can offer you this data in the following 3 formats:
>
> - iCalendar
> - ASCII text
> - the mandatory JetSend encoding"
>
...
>
> No matter what JetSend device the PalmOS device connects with
> meaningful content
> exchange is guaranteed to happen since both sender and
> receiver must support the
> mandatory JetSend encoding (300dpi, 1-bit mono, RLE
> compressed raster data).
Yark! The -mandatory- format is 300dpi bitmap!??! You're
talking memory-limited & sometimes low CPU power devices here.
Wouldn't it make more sense if the mandatory format were more
of a lowest common denominator kinda thing (like ASCII) & the
bitmaps were an optional format?
Bitmaps may transfer a -picture-, but they don't really transfer
the -information-. An ASCII encoding would ensure the information
got across in a format that was more likely to be usable ... at
least to other PDAs, or the humans running them. The bitmap format
is really only useful for imaging devices like printers & faxes.
IMO you really made the wrong choice for your -mandatory- format,
and I think you'll be having a lot of trouble getting buy-in
from the handheld community.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
