started on logging work

[Chad Whitacre]

Hey all,

I started two projects that will form the core of 0.8:

- Decoupling the handler infrastructure: this will now be
implemented as an application, so that it is easier to turn
off, or use at a non-root location.

- Logging: I've started converting print's to logging calls,
and this is forcing me to think about how I want to expose
logging configuration on the command line and in aspen.conf.

The former is kind of forcing me into the latter, as a nimble way
to talk to the application is very helpful in development.

chad

[iGL]

Chad Whitacre wrote:
> Hey all,
>
> I started two projects that will form the core of 0.8:
>
> - Decoupling the handler infrastructure: this will now be
> implemented as an application, so that it is easier to turn
> off, or use at a non-root location.

Hi Chad,
+1 - it's an excellent thing to have a transparent handler API.
BTW, have already elaborated the protocol/inteface?

greetings,
Giorgi

[Chad Whitacre]

Giorgi,

>> - Decoupling the handler infrastructure: this will now be
>> implemented as an application, so that it is easier to turn
>> off, or use at a non-root location.
>

> +1 - it's an excellent thing to have a transparent handler API.
> BTW, have already elaborated the protocol/inteface?

I think we might be crossing wires. Could you help me understand
what protocol you're asking for here?

Thanks.

chad

[iGL]

Chad,

> I think we might be crossing wires. Could you help me understand
> what protocol you're asking for here?
>

I was thinking about app loading protocol - to run several apps of
diffenrent frameworks on one aspen instance, but right now task No 1
is to run 1 django app as fast as on fastcgi...

giorgi