J
Jason
We are in the beginning phase of a rewrite of our Extranet from
Java/BEA/Orace to .NET/SQL Server.
Unfortunately, one of our customers has standardized on Netscape 4.77.
Because they have 20,000 users of our system, we are forced to support this
version of the browser. However, we prefer to NOT be constrained by this
severe limitation for the vast majority of customers who are not
standardized on such an old version.
So, my question concerns the best way to handle situations such as this?
IOW, are there best practices that will allow us to gracefully downgrade
without having to double the coding effort? For example, design patterns
such as MVC, etc.
Java/BEA/Orace to .NET/SQL Server.
Unfortunately, one of our customers has standardized on Netscape 4.77.
Because they have 20,000 users of our system, we are forced to support this
version of the browser. However, we prefer to NOT be constrained by this
severe limitation for the vast majority of customers who are not
standardized on such an old version.
So, my question concerns the best way to handle situations such as this?
IOW, are there best practices that will allow us to gracefully downgrade
without having to double the coding effort? For example, design patterns
such as MVC, etc.