On Today at 3:31pm, KW=>Kirk Wylie <[EMAIL PROTECTED]> wrote: KW> Note lots of snipping. KW>
No problem. KW> [..snip..] KW> KW> Obligatory Monty Python quotation: "What's wrong with a Kiss, boy?" Kiss = Keep it simple stupid, I hope? ;-) KW> Why not just grab it in the cron job and serialize it to a file using KW> plain old Java serialization? Or, failing that, using the new-fangled KW> 1.4 XML encoding? This sort of thing is very well handled by the VM KW> (and serialization has been stable/consistently stored for several KW> years now), so why create extra work for yourself? I hear ya. However, I just replied to Vic's reply and here's the skinny. My situation is different because the call to the data layer for the specific purpose of downloading the application-wide settings is not available yet via java. It is only available, at the moment, via a C API, which is why I mentioned the daily cron job which could be used to generate the "data files" (failed to mention in orig msg that it is written in C). That's life. You gotta deal with what's available. So, serialization and xml encoding are both out the door. KW> KW> Admittedly, it might be nice to use a full caching system to control KW> how often things go to the database using your DAO system for hte rest KW> of the model, but if you're already working fine with this model why KW> not just keep it but use some type of built-in serialization? KW> KW> Kirk Wylie KW> M7 Corporation Thanks for taking the time to reply. -- Haroon Rafique <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
