238 karma · joined January 29, 2011
It sounds like they're doing just this in spirit by backporting some features to Windows 7, but calling it Windows 7.8 instead of Windows 8. Marketing mistake?
I think I gave a pretty poor example in the question, not explaining exactly what I was confused about. Say I have an Auth module with a full suite of methods (login, logout, etc.). Supposed I had a client request a customization that not only requires a username/password for login, but also (as a contrived example) the user's employee number. I'm not sure how to setup the application architecture to (1) easily allow modification of the Users table to include an "employee_number" field (2) update the Auth module to check for employee number in the login function and (3) modify, say, the Login module to update the form that displays the username/password/employee number fields.
My ultimate goal is to work some system where the Auth module/Login module/database tables did not have to be directly changed, so software can still easily be updated.
My big problem is how do I let customers modify the modules themselves, without actually modifying the module? E.g. I'd like to some how give them the ability to, say, add company specific fields to the pre-existing User module and database, without actually modifying the User module source. I'm not sure how to handle the database.
This is the goal for me so future updates can be seamless, no matter how extensively customized their actual version of the application is.
This specific problem definitely wouldn't affect our aircraft simply because they would be at such a high altitude. Even if it was a problem, the military also has a some pretty impressive anti-jamming capability.
BTW, I'm not a pilot, but I work for a government aerospace contractor, so I have some experience in this.