Server architecture of Tine 2.0

From Tine 2.0 - Wiki

eGroupWare 2.0 perfectly fits into existing environments as it ties together many stable and well known server products. It only provides those components related to modern collaboration - which are not delivered by traditional server products.

eGroupWare 2.0 itself is divided into two major components. There is a server component on the one hand, which acts as a service provider for the client component on the other hand. Different from other collaboration vendors with web interfaces, eGroupWare 2.0 does not deliver HTML to its clients.

The eGroupWare 2.0 client is delivered as a Javascript program, with the big advantage that it runs out of the box in any standard browser. And a browser comes along with any common desktop computer. For the eGroupWare Javascript client, the HTTP server acts as an application deployment server for the first request. All following requests are transferred using the JSON protocol and only exchange data.

Why no HTML? Traditional Web-Apps use HTML as output, but this limits the applications in various ways. Most noteworthy are interoperability, performance and connectivity. With the new Service Orientated Architecture it is possible to provide a desktop like application, capable of managing data from different services. Thus the eGroupWare client becomes a true replacement for traditional FAT PIM clients.

Moreover much computation time on the server side is saved, as the user-interface - as part of the client - runs completely on the users computer. Please take a look at the performance analysis page to get a clue about the dramatic enhancement of scalability these changes bring.