• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Design Question

 
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Quickly some background information to my question.

I have been developing a web based application for different labs under our company umbrella. Each site is running basically the same code under a different context name.

I am at the point where it's a nightmare trying to keep up with the different versions/revisions of code for each site. I say versions as in I may enhance code on one site or fix a bug and then get drug off this project onto another and dont update the other sites. It's messy.

I want to consolidate everything. I am already set up where all my SQL calls pass in the context name to call stored procedures for that specific site - that is how I got away with using the same code without hardcoding anything..

What would be the best way to provide one context that multiple sites can hit but only see their personalized information without doing some sort of user authentication/login stuff. Security isnt a big issue but data needs to be kept seperate - that is the main issue.

Any advice would be appreciated. Thanks
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm not sure I fully understand your problem.

Is your main problem keeping all the contexts up to date, or managing the differences and commonalities in the code base?

If it's really the former, couldn't you automate updating the contexts? That is, when you have fixed a bug, you only have to call a script that automatically updates all the contexts at once, including applying all necessary customizations?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic