By doing a MySQL, Oracle or other relational DB backend we are not really
limiting scalability... The whole reason these DB's exist is for precisly
the kind of work we are talking about. Sure, if you do giant table with
100's of fields you are doomed, but a good DB design book will set you
straight... And I have NO intention of putting 250k files on my system.
Under windows you'll find directory access slowing down considerably.
By having fine granularity in the server we are not making client side stuff
more complicated. The server side CAN be complicated (which it really won't
be in the end) or at least fully featured, but it can mimic the Http cddb
protocal for all we care on the frontside. How much easier do you want it.
It can also provide a CDIN or Cdindex or whatver output for newer
generations of players.
Then there was some comment about not changing the CD id... I think that has
been covered before...
August