Bruce's Blog

Bruce, thanks a lot for your input.

Regarding the one OpenNTF signer id - there is a good discussion in ideajam. If you actually want to rely on this id to run applications directly in your environment OpenNTF would need a new process for how to ensure that all code signed by the id is good. I don't see how this could be done practically right now. It feels like a big administrative overhead and something that might prevent people from contributing code.

Regarding the replication of templates - I admit that I don't understand yet, how exactly this should work. I guess OpenNTF would have to provide a server allowing anonymous access so that different servers can access the templates. But then how do you define what templates to replicate, whether you want to get the lastest versions of all them, ...?

We want to allow more web applications to be hosted on OpenNTF directly as we've done it for the XPages demo app recently. From the new catalog you get a link 'run online' so that you can see the app in action. For rich client components the catalog supports drag and drop to install client plugins. That doesn't answer your question regarding 'auto-deployment' though.

In an IBM design partner call a couple of people asked for a new project/tool that helps installing applications. For example it could help you signing databases, creating full text indexes, setting access rights, doing the minimum configuration, etc. I haven't had the time to really think about this yet but it seems like you could benefit from such a tool too and we should think more about this.