Packages

The scope of the Telefrag project is broken down into these components/phases:

Status	Package	Description
80%	Telefrag.Common	Common utilities and constructs; required by all other packages.
80%	Telefrag.Bots	Bot API functionality; exposes Bot which allows sending and receiving Updates and Events at a low level. When using or deriving from Bot, all update handling, string parsing, state tracking, etc. must be done by the consumer.
35%	Telefrag.Bots.Toolkit	The Toolkit is a layer that adds higher level abstractions such as Command, Callback, Menu, Code, etc.
80%	Telefrag.Security	Provides the default authorization model/security framework
0%	Telefrag.Bots.Utility	UtilityBot is a bot useful for diagnostics or learning the Telefrag framework. It allows debug and diagsnotics access to Telefrag via Telegram.
0%	Telefrag.Clients	Client API functionality; exposes Client which allows connecting to Telegram as a full self-contained MTProto client.
1%	Telefrag.Data.SqlServer	Allows use of a SQL Server as an ObjectStore (do we really need this??)

The following components were previously a part of Telefrag or its design and have been put on the ultra-distant back burner:

Status	Package	Description
ND	Telefrag.Hosting	Provides the framework needed for hosting Telefrag as a dedicated background service (including embedding the ASP.NET pipeline) with administrative control and management
ND	Telefrag.Hosts.ConsoleHost	Console host (Kestrel/HTTP.sys)
ND	Telefrag.Hosts.ServiceHost	Windows Service host (Kestrel/HTTP.sys)
ND	Telefrag.Hosts.IISHost	IIS host
ND	Telefrag.UI.Web	ASP.NET-powered web administration console
ND	Telefrag.UI.Studio	WPF-powered thick administration console