Re: [Addanc-developer] Config File for Recorders

[Doug F. <dou...@do...>]

Quoting Joe Griffin <joe...@us...>:

> Just a couple (four really) of comments/questions:
> 1.- We probably do NOT need a console recorder right away. The
> instrumentation
> data stream is huge...and not very useful on the screen. (Am I interperting
> the
> function of a console recorder correctly?) And, useful info can be obtained
> using tail/grep on the file recorder output.

The consoleRecorder is the fileRecorder with 'print' instead of 'write'. I threw
it in to have a variety of recorders. I won't check it in: it's easy enough to
recreate if the need arises.

>
> 2.- The end of the appsettings should be:
>                 <!-- Non-command line configuration option(s), DO NOT DELETE
> any
> of the following lines -->
>                 <add key="connectthreadcount" value="6" />
>                 <add key="vc_inventory_level" value="4" />
>                 <add key="max_new_vc_queue_depth" value="100" />
>                 <add key="max_run_queue_depth" value="0" />
>                 <add key="max_process_queue_depth" value="0" />
>                 <add key="max_wait_queue_depth" value="0" />
>
> (I may not have checked in an up-to-date .config file for the brick.)
>

I'll add these guys. We'll probably still have to merge the final form. Note
that at one point you suggested a scheme for checking in config files without
trashing users active files. This might be a good point to implement that.

> 3.- Does this mean we can drop the config line:
> <add key="instumentationfile" value="addanc.brick.instrumentation" />
> and have the output handled by the fileRecorder?

Yes

> 4.- If yes, can we have the default name for the fileRecorder match the old
> default, "addanc.brick.instrumentation"?

Affirmative: I'll fix it right now.

--
Doug Fort
http://www.dougfort.net
------------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
sec...@do....
------------------------------------------------------------------------
This mail sent through Downright Software's implementation of HORDE/IMP.
For info, see: http://horde.org/imp/