event_system:
                draft implementation of	repeated events	(we still have none defined by protcol)
                more appropriate names for some	enums and structs
        messaging:
                a bit of refactoring in	server_session (cut message handler to separate functions for each message type)
                more appropriate names for some functions
        curl_downloader:
                updating downloaded size variable during download process (thread safety required)

	all projects: corected cflafs/cxxflags
	modules:
		metadata_flat:
			fixed crash on non-existing setting check
client:
	enable ui only after events subscription to avid hypotetically not handled events

	flat_metadata_module: added missed cflags for relase build
	curl_downloader_module: added missed cflags for relase build

added few comments

	curl_downloader:
		correct use of default download_path

	curl_downloader_module:
		implemented metadata cleanup on download delete

	curl_downloader_module:
		basic data transfer handling (now able to save file, still need a lot of validation)
		some tracing code

this may be called first working prototype with vary basic functionality implemented.

currently udm have working server, working qt client and able to download url via curl module (most of additional events like
download progress currently not
implemented, code need lots of sanity checks and exception handling)

	download completed state
client-qt:
	added "download completed" subscription and status support
server:
	module_curl:
		used events api in core for download state changes
	core:
		download completed event support for modules

updated copyrights (new year)
server:
	started implementation of api for module events (module should be able to fire event which will be delivered to clients which have subscribed for this event type)

	a bit of work with "client_event_subscription_request"
	some comments
server:
	event subsystem:
		event's object class skeleton
		very basic event subscription handler