issue 153:
Added general tmp location using new Param:tmp_path with default value: ~/.bbfs/tmp
content data (server & backup) is first written to ~/.bbfs/tmp/tmp_content_data and then moved to user provided location to store the content data
issue #148 done.
Monitor log uses general log params: log_flush_each_message and log_rotation_size.
It has also its own param:default_monitoring_log_path
Other then this it is independent of the general logging system.
Enbaled with basic variables:
{server_name:content_server} ,
{time:2013-06-09 14:48:18 +0000} ,
{monitoring queue size:9397} ,
{content data queue:1} ,
{indexed_files:4192}

To use it pls add the following parameters in configuration file:
#process variables monitoring
process_monitoring_web_port: 5556
enable_monitoring: true
process_vars_delay: 2

To use it type in browser:   server_name:port_number
for example: localhost:5555
Refresh the web page  to get latest values (values are updated every number of seconds according to value in param-process_vars_delay
Enhanced proccess monitoring to count objects (content_data, FileStat, DirStat and more) allocations and disallocations.
Change monitoring so that is stable_state = 1 then at first occurence of file\dir the state of it is STABLE
1.Fixed typo bug of to_s of file monitoring
2.Removed unnecessary process var object
Added process monitoring capablity to cound ALL living objects under the process.
This can tell us if over time there is a memory leak
Added process monitoring capablity to cound ALL living objects under the process.
This can tell us if over time there is a memory leak
fixed bug where if monitored file does not exist during indexing an exception was raised. Now only warning is written that file has probably changed
Added String object count to Process variable monitoring feature
1. Enhanced gem build scipts from patch_1_0_3 (still need to change versions for 1_1_0)
2. Enhanced process var monitoring to print more usfull data to log and web
3. returned file_monitoring to original behavior of stable_state parameter
4. Fixed issue were Sinatra accepted connections only from localhost. Now all connections are accepted
Issue #162: Update "backup_destination_folder" flag.
yml parameter changed to:
  backup_destination_folder:
    path: ~\Ruby\Git\TestRoundClock\backup_server_root
    scan_period: 5
    stable_state: 1
typo
fixed issue where ~ was not expanded in bakcup_destination_folder and caused files not to be copied
Removed 'device' from all content data code since it is a 1:1 relationship with the full path
issue #156 fix
1) Alexey fix. 2) Change content data usage from emutable to mutable database. 3) Fix minor issues.

Merge remote-tracking branch 'origin/master' into release_1_1_0

Conflicts:
	lib/content_server/backup_server.rb
	lib/content_server/content_server.rb
	lib/content_server/queue_indexer.rb
	lib/file_monitoring/monitor_path.rb
Merge + Alexey changes + Content Data changes + Small issues changes.
Merge remote-tracking branch 'origin/release_1_1_0'