> > I ask because I'm thinking about doing "picture messaging" for a consumer > market where the user sends messages with cute pictures attached to them. >
Why not just send URLs to images in band? > Given the doc above, they shouldn't be sent in-band; so I was thinking of > doing some sort of caching on the recipient end since the sender has only > so many pictures to choose from. If the recipient does not have it yet, > then they will be given a choise to fetch it via HTTP, possibly from a > "trusted server." The pics can be located anywhere. What might be cool, is to find a free web provider that offers webdav. You could have your jabber client upload your images automatically to your free webspace via webdav and link them into your messages. If you used a good HTTP library, it might do that caching for you. Remember that clients participating in this will need to know how to render HTML messages. For usefulness, clients will need an easy way of inserting these HTML tags. I'm sure you've already thought of that, though :) Mathew Johnston > > I got the picture messaging idea from Nokia mobile phones. > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
