Dallas Gutauckis wrote:
> Hello all,
>
> I am interested in having a specification to define how a server might
> let a client know certain binary data is available via HTTP.
>
> I'm working on a Javascript BOSH client and it would be useful if the
> server made available to me certain data (like user avatars) in their
> "natural" form such that I would be able to make use of a standard image
> tag with http://... as the `src` attribute, instead of using the base64
> as the `src` (which some browsers do not support)
>
> I also see that this might be useful for the purposes of having the
> server handle file transfers for a javascript client (which would not be
> able to handle an ordinary XMPP-defined file transfer) It is suggested
> that the server might download the file, and make available to the
> client (when complete) the address (and possibly other data pertinent to
> a file transfer) from which a user (via web browser) might be able to
> download said file.
>
> Please let me know what you think, and how we might structure this.
We have a way to include the HTTP URL for an avatar or whatever (from
XEP-0084):
Example 4. Publishing avatar metadata
<iq type='set' from='juliet at capulet.lit/chamber' id='publish2'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<publish node='urn:xmpp:avatar:metadata'>
<item id='111f4b3c50d7b0df729d299bc6f8e9ef9066971f'>
<metadata xmlns='urn:xmpp:avatar:metadata'>
<info bytes='23456'
height='64'
id='222f4b3c50d7b0df729d299bc6f8e9ef9066971f'
type='image/gif'
url='http://avatars.example.org/happy.gif'
width='64'/>
</metadata>
</item>
</publish>
</pubsub>
</iq>
Do you want a way for the publishing entity to find out from the server
what the URL is? That is, when I configure the avatar in my client, the
client sends it to my server (or simply publishes it) and the server
tells the client the URL at which the data can be retrieved via HTTP?
Peter
--
Peter Saint-Andre
https://stpeter.im/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20080324/91b312d5/attachment-0002.bin>