[Topic] Server: Why?

OK, I went to a fair amount of trouble to set up the server, and then I go to the client and it appears as though the client talks directly to the database. So why use the server at all?

—Posted by James on Dec 8, 2006

for collaboration through internet, especially if you want to allow people without AgileTrack client to access it. actually, if access is open to public you wouldn't want to allow users access DB directly.

—Posted by slava on Dec 9, 2006 at 9:10:45 AM

In a single user environment there aren't many reasons to use the server.

In general, like slava said, database security and Internet accessibility are currently the main reasons.

The AgileTrack server also provides JSON-RPC and XML-RPC access interfaces that can potentially be used as integration points with other systems. Currently they aren't documented, but that will change as the AgileTrack documentation is completed.

In some cases, the server can provide better performance than a direct connection to a remote database. This assumes the server has a low latency connection to the database, but the remote clients do not. The JSON-RPC and XML-RPC interfaces are higher level and require fewer round-trips to interact with the database than with a direct connection. However, in most LAN environments, there wouldn't be any noticeable performance difference.

In the future, there will be a web interface that is distributed with the server, but that is still months away.

—Posted by Adam Lane on Dec 9, 2006 at 11:43:40 AM


You may post a reply to this topic, but you must be logged in. If you already have an account, you may login now. If you need to create an account, you may also register now.