benglerpebbles/kcuts — Issue #5: Preconfiguration mother fucker 
Author: tomkoptel
Created: 2012-01-18 12:25:36+00:00
State: open

if
`hail http --requests 10 --workers 10 --url ya.ru`
then
` cli_options = { :request_count => n, :worker_count => m , :url => "ya.ru" }`
else
`hail (http || sql) --workers 10 -- config (routes.yml || sequel.sql)`
then
` cli_options = { :request_count => n, :worker_count => m , :path => "routes.yml" || "sequel.sql" } `
end :)

```ruby
config = Kcuts::PreConfig.new(basic_options)
# will start Forking, Execution, Benchmarking, Aggregation
Kcuts::HTTP.new config
# or
Kcuts::SQL.new config
```
PreConfigurator will be responsible for parsing files (.yml, .sql) and will return the appropriate object.
So for example for `database.yml` file transferred to the cofigurator we would have:
`config.db.host # => 'localhost::9090'`

Neither me nor Edgar likes idea of `Kcuts.new( :http, cli_options)`. It makes more sense to use utils within Kcuts which are structured for the specification (sql or http) `Kcuts::HTTP || Kcuts::SQL`