|
> The changes made to a datasource are not dynamic ..... >they need to stop and start the server to pick them up. Yuck! Net effect is that I have to bounce the server to add a library to the list? Yuck. Case in point, I needed to add a library to a data source yesterday for new functionality in _one_ of several applications on the server. I have to bounce all the apps on the server to add functionality to one? Yuck. >Furthermore, you should NEVER, >NEVER "kill the server side jobs". I know, but I was willing to accept those errors, each app has it's own datasource so at least I'd only effect one of the apps, not all of them. Does 6.0 have the same limitation? And what's the "best practices" then for deploying apps? One app server per datasource so if you need to mod a datasource you don't need to bounce all the unrelated apps? -Walden ------------ Walden H Leverich III Tech Software (516) 627-3800 x3051 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.