Posted by: AmCorp.it* Jul 15 2007, 06:48 PM
There are now some news available about TeamSpeak 3 client:
TeamSpeak 3's Core Architecture
OK, for all you techies and brainiacs out there, we are developing the client in two layers, the core part which we usually refer to as the ClientLib and the interface part which we call the ClientUI. The ClientUI uses the ClientLib to do all the interaction with TeamSpeak 3 servers (like connecting, disconnecting, creating channels, etc). The ClientUI is responsible for the user interface (hence UI), as it presents the user with dialogs and windows showing information retrieved from the ClientLib (e.g. the channel list in a tree view) and it allows the user to issue commands (e.g. right click on a user and kick client) that are submitted into the ClientLib which carries the command into execution. The advantage of this modular approach can easily be seen from a developer's point of view. When anybody wishes to create an entirely new user interface, he just takes the existing ClientLib , and substitutes our ClientUI with his own completely custom interface.
http://www.teamspeak.com/images/blog/ts3_architecture.jpg
The four boxes at the top are the things a regular user is most likely to encounter.
- The 'graphical user interface' (Qt) is the main TeamSpeak 3 client application, similar to what you use currently in TeamSpeak 2. Note, however, that TeamSpeak 3 will now natively support Macintosh, Linux, and Windows platforms (hooray!).
- The 'console user interface' is currently used for stress testing a TeamSpeak 3 server with bot-like clients, but depending on the lua script (scripting language) it is now capable of doing just about anything you can imagine!
- 'Telnet' and 'Scripts / Programs, 3rd Party, Web Interface' all use our new powerful query interface similar to TeamSpeak 2's TCPQuery but much more powerful. In addition, the web interface is now an external PHP script which can be used to administer a TeamSpeak server via a web browser.
- ClientLib/SDK is a library (dll/so) which makes it possible to interact with the server by using its simple programming interface. So, it provides the possibility to for example connect to a server, mute the microphone, or switch channels. The Capture/Playback/Input components are going to provide a plugin system which allows you to for example write your own playback plugin which streams the output to a shoutcast server in addition to playing it back. Although the UDP protocol is a superior choice for real time voice communication, TeamSpeak 3 will also provide the option of using TCP instead of UDP. Support for TCP connectivity is particularly useful for circumstances where people need to use proxies, or where UDP is completely blocked due to corporate firewalls, etc.
- Server is fairly self-explanatory, we will support a database plugin system so for example you can write your own plugin for a completely proprietary database if you wanted to. The server components will also be available as a library version to include into your own application.
Read more at http://www.goteamspeak.com/index.php?page=blog