wolf at bluehands.de
Thu Jun 24 08:35:35 UTC 2004
I would like to keep the possibility to send inline data. There is a serious karma problem with images. But there might be cases where the avatar data is not that large. I am talking about cases where the avatar is not as large as an image file. I only want to point out that avatars are not always images. So, karma is not always a problem when publishing avatars. Hence, the protocol design should not require a file-transfer.
Question 1: Can we make both (file-transfer and inline) possible?
Question 2: Can we also have a URL as data source? Also solves the karma problem even for images.
Question 3: Would it be possible to not always base64 the embedded data. Again: if it is not an image then plain data might be nice.
Question 4: Would it be possible to specify the encoding of embedded data?
In my project we are using 'storage:client:avatar' storage for avatar data. I love the simplicity of the 3 possibilities:
<data mimetype='image/png' encoding='base64'
Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
+49 (0721) 16108 75
LLuna: Jabber enabled virtual presence on the web / http://www.lluna.de/
Galactic developments: Open source future history / http://www.galactic-developments.com/
> -----Original Message-----
> From: standards-jig-bounces at jabber.org
> [mailto:standards-jig-bounces at jabber.org]On Behalf Of Peter
> Sent: Thursday, June 24, 2004 1:30 AM
> To: standards-jig at jabber.org
> Subject: [Standards-JIG] avatars
> I haven't seen many comments on temas's proposed updates to JEP-0084:
> This seems like a good approach to me and I'd love to read an
> updated JEP
> that spells out the changes in more detail. :-)
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards