Seperating portal-driver into api and impl

[David H. DeWolf]

All,

We've had some new interest by different portals wanting to embed pluto. 
 Specifically, I'm helping Sakai embed pluto into their  portal and 
there may be a couple of other open source portals wanting to do the 
same after we have success with Sakai.  This is obviously good news for 
our community.

In order to assist with this, I'd like to separate out the portal-driver 
into an api (interfaces) and an impl project.  I know we've discussed 
not making the portal too feature heavy  (since we're really a project 
about the container), so I wanted to discuss this before I made the 
separation.

IMHO this won't make anything more complex since I won't be adding 
anything additional, it will just create a clean separation so that 
others can more implement robust solutions (such as db driven 
implementations) without having to worry about the impls provided.

I've got the refactoring ready to commit. I'll wait till I hear from a 
few of you before I make the change.


Thanks,


David