IspCP as a VHCS Omega stripdown

[Kermit]

Just some thoughts...

as said in a previous post, VHCS Omega is composed by some modules working side by side, as webmail, webftp, sql-panel and (in the future) dns panel, ticketing system, and so on.

When IspCP as a general framework will be ready to go, VHCS Omega will be integrated as its default hosting-panel. At that moment, will all that modules mentioned above be thought to "raise one level", being stripped off of the VHCS Omega itself to be managed by the main IspCP framework?

I think this could be a good point: first of all VHCS Omega will be very lightened, it will require less effort to be put in place and maintaned... and it should be easier to make the architeture much more "modular".

Ok, I know, nothing useful here... as I told, just thoughts ^_^'
Sorry