TheCryptowizard
27-11-2005, 03:52
Old Post: http://forum.goteamspeak.com/showthread.php?t=5313&highlight=XML
That's about all I could find on this subject before I posted this. So if I am stepping on anyone's feet, please say so.
I think it would be an excellent idea for the developers of TeamSpeak to utilize an XML schema. This would allow effortless integration with other applications and expand the usability of this program.
For example, if there is a program that is written in a different language and doesn't have a specific API for teamspeak, they could easily integrate it with teamspeak via a common API ... xml formatted data. Standard users could simply chose to have their XML data ported directly into an SQL/MySQL database - or they could leave the API open for other uses.
As it stands, many people have issues converting the DBS to a MySQL. Though it is not terribly difficult to make this change and support IS available for this feature, it would have been a lot easier if the original format had been XML. Then people like me could write an application that could directly manipulate the teamspeak server and permit the means for powerful plugins.
I know for a fact (from reading previous posts by the developers) that there are plans to improve the database backend of this application. I can only hope that XML is a part of it. It would expand "their world" a million times over and give them an exceptional edge in the VoIP software industry.
That's about all I could find on this subject before I posted this. So if I am stepping on anyone's feet, please say so.
I think it would be an excellent idea for the developers of TeamSpeak to utilize an XML schema. This would allow effortless integration with other applications and expand the usability of this program.
For example, if there is a program that is written in a different language and doesn't have a specific API for teamspeak, they could easily integrate it with teamspeak via a common API ... xml formatted data. Standard users could simply chose to have their XML data ported directly into an SQL/MySQL database - or they could leave the API open for other uses.
As it stands, many people have issues converting the DBS to a MySQL. Though it is not terribly difficult to make this change and support IS available for this feature, it would have been a lot easier if the original format had been XML. Then people like me could write an application that could directly manipulate the teamspeak server and permit the means for powerful plugins.
I know for a fact (from reading previous posts by the developers) that there are plans to improve the database backend of this application. I can only hope that XML is a part of it. It would expand "their world" a million times over and give them an exceptional edge in the VoIP software industry.