On Sat, Mar 8, 2008 at 2:25 PM, Steve Loughran <[EMAIL PROTECTED]> wrote: [...] > We in SmartFrog, http://smartfrog.org/ are assing support for Restlet > deployments as manageable components, but I don't consider the stuff > stable yet. I've finally got all my tests with S3 working, with > through-firewall communications and the ability to set the access > rights with custom http headers. That's the client done, so the server > comes next; Jetty is something we've supported for ages.
Cool! [...] > > So, it's best to presume that your Java application may be killed at > > anytime. I.e., make sure that your code deals appropriately with the > > error conditions that that may cause in some reasonable way given your > > application's semantics. > > See Crash Only Software : http://crash.stanford.edu/ :-) Indeed, they take the view to the extreme. > No matter how well you design handlers in your app, you cant stop the > VM the OS runs in being killed without warning, you can't stop the > laptop power failing. Stop treating unannounced termination as an > unusual event and your software meets reality more accurately. Indeed. One of the issues with extreme approaches ala "Crash Only Software" is that they can be unnecessarily graceless and inefficient. Rock on, John
