Interests: Developing web and mobile apps
Hobbies: Writing great code that helps people and businesses get stuff done. Love pizza, good music, good friends and beach combing.
Subscribe via Feed
, Jun 15, 2010, 1:18:58 PM
3 responses to Single Copy XPage Design, another piece of XPages magic!
Marius, July 23, 2010 at 8:47 AM
Why not a Single Copy Template / what are the benefits over Single Copy Templates?
Paul Hannan, July 15, 2010 at 6:53 AM
Yes, you are correct on the risk of database corruption. Though this risk would be lessened somewhat as the data on the other databases would still be preserved and unaffected. And the turnaround time to addressing the issue (replacing the corrupt db with a backup copy) could be swift.
On the performance side of things there shouldn't be a hit in the scenario this feature is meant for - the browser accessing many apps of the same design. Performance would be improved here.
This is a great feature though I think it wouldn't fit everyone. If your organisation has many apps of the same design, why upgrade them all when you can just do the one? And if your users are working with multiple apps of the same design from a browser or XPiNC, then this could be the feature for you.
Phil Warner, July 14, 2010 at 9:20 PM
I've been advised in the past that this sort of thing was bad practice, both in terms of performance and exposing the risk of your entire application breaking if your central resource database becomes corrupt or gets accidentally removed. What's different here? This is a tremendous feature if it's robust.