Architectural question
Architectural question
I'm getting ready to start on a fairly large project and I'm not quite sure which approach I should be taking. This is going to be a music library site where a music supervisor would log in and browse the available songs using different criterial to filter the list. Right now the data is in an iTunes XML file and will probably remain there as the master offline copy that is maintained by the composer.
I'm just getting into jQuery but I'm thinking that it might be a good solution for this. I'm thinking that I could create a "one-page" site where the XML file is loaded by jQuery and then the page is dynamically re-rendered as the visitor selects new filtering criteria.
This iTunes XML file contains data for over 3000 songs and is nearly 5 MB. I may end up creating a PHP preprocessor to rewrite the iTunes XML file into a more compact form. I can probably get the file down closer to 500-600 K.
I'd love to get input from anyone who's got jQuery experience as to the wisdom of jumping headfirst into a project of this scope with little jQuery experience.
For reference I've been doing a lot of PHP work over the last several years and I've got a good feel for DOM structure. I've also got a reasonable working knowledge of AS3 and way back I did VMS C programming and Apple ][ coding before that so I'm no stranger to programming.
TIA