The PureMVC Framework Code at the Speed of Thought

Thanks for such a wonderfull util lib. I'm realy anjoying it's simplicity and understandability.

Two question have appeared when playing with pipes:

1. Messages are most likely relative to data part of an application, rather than to it's view. And generally mediators in PureMVC are used to mediate between "flash" view components and "flash-less" core. So why junction mediator? Why not some sort of junction proxy? Though I can understand that mediator pattern is more general than it's commonly used in PureMVC.

2. There is an already done (thanks for helping lazy coders) method in JunctionMediator

public function handlePipeMessage( message:IPipeMessage ):void
{
}

For me it's a bit strange why it's public. The only thing I can guess why it's public - it can serve as a usual function, rather than just pipe listener. Thus we can make some custom message inside module core and pass it to that. But the method is specificaly made only for pipe listening. I'd make it protected for sure.

3. Sorry for my english