Any hope of seperating playlist from CDJ?

No doubt about it -- CDJ and Slinkx are getting cooler every day. But I'm having two key problems these days, both of which would be solved (I think) by seperating the playlist engine into a seperate ActiveX component, and having CDJ be the frontend to that. My problems are

1) I have 4 systems in the house that I use CDJ from. Two that I use all of the time (upstairs/downstairs). I've got DCOM going and I'm using a mdb file on a central server, but I can't run CDJ on more than one system at once without causing total chaos.

If CDJ were merely a frontend to the playlist component, that component could run on the same server that SlinkX does, and be the one in charge. If I added a song/changed modes/whatever from one station running CDJ, the others would pick it up.

The alternative is running PCAnywehre and just running CDJ on the system that the Slinke is attached to. But that still limits remote access to one computer at a time, and it stresses out my win95/16mb laptops badly.

And 2) the event driven nature of the automation interface just doesn't work well with ASP pages. If the playlist were split into a seperate component, it would make more sense to add functions that returned the currently playing song, number of songs in the playlist, and so on.

On the whole, CDJ is a great win32 frontend to the whole Slinke/SlinkX product and system, but it seems like it would make more sense to have a layer of abstraction between CDJ and SlinkX, for these reasons. Let that middle layer fire off events at CDJ that tell it when things change, and then CDJ could co-exist on multiple machines, or in conjunction with web interfaces or anything else someone comes up with.

What do you think, Colby? I'm sure you've got *so* much spare time with the DXS and all...