[ticker-dev] Why Attachment field as byte array?

[David Arnold]

-->"Ian" == Ian Lister <ilister at dstc.edu.au> writes:

  Ian> What about allowing it to be either an opaque or a string (but
  Ian> still forbidding any encodings that aren't currently allowed)?

there're no encoding forbidden now, it's just that they're not
necessary?

  Ian> That way simple stuff can still be dealt with simply, and is
  Ian> available to be routed on.

i worry about 

   contains(Attachment, "x-elvin/url")

being evaluated over images and Word files.  it's gonna chew a lot of
CPU.  making it opaque prevents this nicely, and makes people route on
the "content" (as distinct from the attachment).

but does it break people's usage?



d

ob-lawley:
  if elvin had structured notifications, a better solution would use a
  list of hashes to make the content type (at least) available for
  routing (and possibly the data for some content types)