# Re: SANE frames

Nick Lamb (njl98r@ecs.soton.ac.uk)
Sun, 15 Aug 1999 23:36:21 +0100 (GMT)

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Nick Lamb: "Re: SANE V2"
- Previous message: Nick Lamb: "Re: SANE frames"

On Sun, 15 Aug 1999, Tom Martone wrote:

> SANE_FRAME_ASCII: The frame contains a stream of ASCII text.

Wouldn't this normally be associated with an image? If so it might be
better to do this as multi-frame, with the ASCII frame followed by
zero or more image frames as appropriate. Then you can explain in the
standard that a frontend is free to throw away the ASCII frame, and
hope there are image frames following it..?

Some image file formats (Oliver, are you listening?) even make some
provision for storing short-ish ASCII streams with the image, in a
more or less general way.

> SANE_FRAME_RAW: The frame contains a stream of bytes (...)

I don't like this much, as everyone already knows, but if it must go
into SANE 2.0 then I'd prefer that it was numbered away from the rest
of the sequence in the enumerated type. I'd also like wording in the
documentation which asks backend creators to suggest new frame types
when necessary rather than using FRAME_RAW.

Perhaps -1 or 65535 or something? I think a signed integer is used for
storing this value, but I might be wrong...

Nick.

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: Nick Lamb: "Re: SANE V2"
- Previous message: Nick Lamb: "Re: SANE frames"