--- Justin Karneges <[EMAIL PROTECTED]> wrote: > Totally random thought: I wonder if Google is legally required (say, > by > contract with AOL) to thwart attempts by third-parties to access the > AIM > integration. What if someone wrote a new Jabber transport that > required 4 > fields: gmail account name, gmail password, aim account name, aim > password? > Would this give the rest of the XMPP world legit access to AIM via > double-transporting? >
Since the Google implementation is a dual headed client so that a single transport wouldnt work anyway to connect to both IM networks other than possibly as a wrapper; and both Gtalk and AIM are fairly open about APIs (XMPP and "legit access" via the OpenAIM program respectively) that you can use to connect to their networks directly - what would this approach accomplish that you couldnt get done with 2 individual transports ? With the OpenAIM program you dont need to piggy back on anyone - but you do need to use the SDKs they provide and there are certain usage limitations imposed by the keys they provide.
