quote:
Originally posted by square87
So maybe a database can be useful to give an unique ID only when a new sound is created and stop. When we want to send a sound we can send at the user a message with ID, then a plugin check if we have that sound in our cache and send an answer that we (don't have OR have) the necessity to download it from the user.
That's exactly what I described before (and how the sound system works). You can implement that already in aMSN. You only can't download the sound directly from the server database.
/ 
