(For the sake of clarification for those reading this from the jig-standards list, the PyAIM transport has an ad-hoc command called 'aimuritranslate', which allows you to 'execute' a aim URI)
So I was thinking about the "aimuritranslate" ad-hoc command a bit, and I was trying to think about a possibly better/generic way to handle it. The problem is that there are some actions that can't be performed in such a way (such as joining a chat room), and some actions that you don't want to execute immediately (such as a URI which fills out a default message to be edited before being sent).
What about having a service which would translate from the legacy URI to the XMPP IRI? This would allow the client to interpret the URI properly under all circumstances.
For example, such a service would translate the following URI's as follows:
might become
...and...
might become
This actually sounds like something that could be applied added to every legacy transport. With proper client support, this would allow a jabber client to correctly support all of those proprietary URI's!
Such a mechanism could be useful for more than just translating legacy URI's to XMPP-IRI's. For example, you could have the returned URI not be an XMPP-IRI at all.
Anyway, I am sending this to both the pytransports list and the jig-standards list because I think the topic has ramifications for both.
Any thoughts?
__________________
Robert Quattlebaum
Mobile: +1(650) 223-4974
