You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by Christian Grobmeier <gr...@gmail.com> on 2009/08/03 10:56:06 UTC

Adobe Wave Appender

Hi guys,

this morning I put together some classes for communication with Adobe Wave:
http://labs.adobe.com/technologies/wave

I think this is an excellent tool. I was thinking about writing an
Wave Appender for Log4PHP.
This would make it possible to have error messages popping up at the
desktop computer,
when they occure :-)

What do you think about it?
Christian

Re: Adobe Wave Appender

Posted by Christian Grobmeier <gr...@gmail.com>.
>> What do you think about it?
>
> Then we'll soon have a TwitterAppender ;)

Why not?

> I think that would be more like a toy and not useful in real life
> applications.

I was thinking on monitoring. I mean, who really monitors PHP webapps
if they are small? A pushed notification would be cool I think. Its
basically the same as E-Mail notification.

>Adobe Wave messages (and others) should be updated through
> some middleware and not directly through log4php in my eyes. That middleware
> should fetch new log messages and put them onto the respective messages
> streams.

Its working like this. Log4php sends notification to Wave Middleware
-> Wave Server distributes it to all subscribers

> Disc is faster than network and if we start supporting all kinds of
> different services out there we'll start creating a lot of unnecessary work
> for us. Let's keep it simple :)

True, about the workload. True about disc. But well, I don't think
this idea is too bad :-)

Cheers,
Christian

>
> Knut
>
>

Re: Adobe Wave Appender

Posted by Knut Urdalen <kn...@php.net>.
Christian Grobmeier wrote:
> What do you think about it?
>   
Then we'll soon have a TwitterAppender ;)

I think that would be more like a toy and not useful in real life 
applications. Adobe Wave messages (and others) should be updated through 
some middleware and not directly through log4php in my eyes. That 
middleware should fetch new log messages and put them onto the 
respective messages streams.

Disc is faster than network and if we start supporting all kinds of 
different services out there we'll start creating a lot of unnecessary 
work for us. Let's keep it simple :)

Knut