• TimeTrak Live is a windows service which uses a Web browser as a client for the user interface.
• TimeTrak Live uses the Component Services functionality of IIS (Internet Information Services) which allows the IIS hosted interface to reside on separate servers from the TimeTrak Live application and/or database servers – permitting distributed work load across multiple servers.
• TimeTrak Live is not hosted inside of IIS, the client only uses IIS as an ASP.Net channel to the main TimeTrak Live application which runs as a Windows Service
• Using the SOA (Service-Oriented Architecture), the application ‘lives’ on the server before, during, and after the user’s session. This is not the case on many Web Applications.

• Because we don't use any ActiveX controls and nothing needs to be installed on the client computer, the TimeTrak Live client will run on ANY browser that supports HTML & Javascript.
• Currently testing:
• Internet Explorer - versions 7.0 & 8.0
• FireFox - version 3.5 (Windows and Linux versions)
• Chrome - version 3.x
• Safari - (Mac OS and Windows)

Why lock yourself into old technologies and restrictions when you can have the freedom available from new technologies?

• Native support for Relational Databases
• Microsoft SQL Server
• Versions 7.0, 2000 and 2005
• Express and MSDE versions available at no cost
• Oracle
• Versions TBA (testing with version 10g for Windows)
• IBM DB2
• Versions TBA (testing with Version 8.2 for Windows)
• Others Possible
• Database Plug-ins for Data Access Layer (DAL)
• Database plug-ins permit TimeTrak Live to access data from many database architectures, and we will add others that meet our data requirements in the future.
• Database Plug-ins for Data Access Layer (DAL)
• TimeTrak Live uses a (DAL) to access all data from the database
• Anytime the application needs data from the relational database system, it uses the (DAL) to request it
• The (DAL) is a plug-in (a .DLL) that has a common interface
• TimeTrak Live asks for data using the standard interface and the plug-in is responsible for getting the data from the actual database server in the most efficient way possible
• The database plug-in will be selected during installation

• Event & Data Marshalling using XML-RPC
• allows software running on disparate operating systems or running in different environments to make procedure calls over a TCP connection
• SOA (Service-Oriented Architecture)
• provides a standards-compliant interface which is independent from the underlying implementation of the service logic. For example, a .Net service could be used by a Java application and vice versa.
• Microsoft .Net Framework 3.5
• .Net-connected solutions enable businesses to integrate their systems more rapidly and in a more agile manner.
• The .NET framework is the Microsoft services strategy to connect information, systems, and devices through software. Integrated across the Microsoft platform, .NET technology provides the ability to quickly build, deploy, manage, and use connected, security-enhanced solutions with services. .NET-connected solutions enable businesses to integrate their systems more rapidly and in a more agile manner
• The Microsoft .NET framework includes everything a business needs to develop and deploy a service-connected IT architecture: servers to host services, development tools to create them, and applications to use them
• Event & Data Marshalling using XML-RPC
• XML-RPC is a specification and a set of implementations that allow software running on disparate operating systems or running in different environments to make procedure calls over a TCP connection.
• XML-RPC is a Remote Procedure Calling protocol that works over a TCP socket. An XML-RPC message is an HTTP-POST request made to the socket. The body of the request is in XML format. A procedure executes on the server and the value it returns is also formatted in XML. Procedure parameters can be scalars, numbers, strings, dates, etc.; and can also be complex record and list structures.
• SOA (Service-Oriented Architecture)
• Service-Oriented Architecture (SOA) expresses a perspective of software architecture that defines the use of services to support the requirements of software users. In an SOA environment, nodes on a network make resources available to other participants in the network as independent services that the participants access in a standardized way
• Unlike traditional point-to-point architectures, SOAs comprise loosely coupled, highly interoperable services. These services interoperate based on a formal definition (or contract) which is independent from the underlying platform and programming language. The interface definition encapsulates the vendor and language-specific implementation. An SOA is independent of development technology. The software components become very reusable because the interface is standards-compliant and is independent from the underlying implementation of the service logic. So, for example, a .Net service could be used by a Java application and vice versa.

• AJAX (Asynchronous JavaScript And XML)
• AJAX is a web development technique for creating interactive web clients interfaces. The result is web pages that are more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user makes a change. This increases the web page's interactivity, speed, and usability and thus the users productivity.
• Asynchronous AJAX Web Refresh Panels – eliminate the flash of standard web page reload and give a truer application experience.
• Microsoft Reports
• Streams reports generated on the server back to the client
• Allows for :
• Viewing of all report data including sorting, filtering, and navigating in an easy to use viewer
• Printing to any printer the client has access to including printers defined at the server
• Emailing to any email recipient
• Exporting to pdf, excel, html, etc