quote:
Originally posted by CookieRevised
Then please explain in great detail what you mean, because what you described here as an example to how it could be done IS exactly how it currently works in Plus! and what you already can program in aMSN without any restrictions (except for the access to the server DB itself).
He wants there to be a second system for sound transfer - Plus users can access the database to upload/download sound when they are sent/received (as they currently do), but on top of that if the other user is using aMSN and the aMSN user does not have the sound (cached or otherwise) then MsgPlus will use the MSNP to send the sound to the aMSN user. Conversely, aMSN users which send sounds will send a sound ID (if the sound exists on the Plus database), otherwise they will send the sound using the MSNP.
Note: I am simply explaining my understanding of square87's suggestion.
The possibly problem I see with this is it is still abusing the MSN Protocol
quote:
Originally posted by CookieRevised
One reason being that 3rd party clients aren't suppose to (ab)use the protocol. Patchou has a very good trustworthy relationship with Microsoft and doing such a thing will compromise this for sure.
/ 
