Glossary

Site Instance (also Site or Instance): There can be more than one instance of the core process of TIMP.NET — TIMPCLRHost. Each one of these instances can host multiple Site Domains that will share the same administrative and performance environment. It is the heart of TIMP.NET and can distribute messages according to the message recipient's domain.

Domain: Each domain managed in the environment of a specific Site Instance will implement the infrastructure necessary to host the components. They may be set up to be either public or private:

• Public - The services associated with public domains will be accessible via an XMPP server or by another separate TIMP.NET instance. The services must be correctly registered in the DNS as an Internet domain that points to the server hosting TIMP.NET.
• Private – In this case the service needs to be implemented using only components associated with the domain accessible from within the same instance of TIMP.NET.

Component: This is a type of .NET class that processes messages (Stanzas) addressed to a domain and it generates outgoing streams of data properly formatted for the recipient. Typical components are transports or gateways.

Filter: This is a type of .NET class that is able to intercept incoming messages (Stanzas) before it gets to the destination component. These messages are then placed in a queue in order to be modified, left alone or filtered out.

XMPP Stanzas (or Stanzas): any XMPP micro-document exchanged between different clients, servers and clients or between servers.

IM Address or JID (Jabber Identifier): each user must be uniquely identified with an identifier such as username@mydomain.com.