I'm looking at how I will distribute the product I'm working on, and so that the WO backend can be easily installed by a semi-pro who doesn't have intimate knowledge of the command line or Apache configuration file.
So I was thinking of distributing the app with it's own version of Apache with the WO Apache module, the app, and wotaskd, and include everything in a .pkg or .rpm. Why including wotaskd? Because I want some kind of watch guard to restart instances in case they crash, auto restart if the server is restarted, etc. Now why I'm not including JavaMonitor? That's simple: I want to reduce memory footprint and JavaMonitor always eat at least 32 MB of RAM, and since a lot of people are using VPS or Amazon EC2 for their servers and have somewhat limited RAM resources. So what I was thinking about is to move the REST routes I added to JavaMonitor down into wotaskd. By doing that I would be able to create a small HTML page with JavaScript to talk to wotaskd and ask for stats, status of instances, etc. By doing so, I need to do some refactoring since some code will have to go from JavaMonitor and JavaMonitorFramework to wotaskd. Any opinions? _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
