I'm already running in client 1.3 code is running, when my work was dependent on the better features of 1.4.
Still these clients do not have the resources to update their old code ...
Example : Clients add jQuery 1.3 to their site templates it shows.
Any thoughts about dealing with this problem?
Edit: The ideal solution will be completely JS ... there is no server-side code because the client likes it like this.
Try to understand the customers that the "resources" need is generally very light. Changing to a new version is usually a very quick process, as long as there was a lot of bad code in it that was previously allowed, but it was wrong.
Let them take a look at them, and for that matter, the benefits of upgrading away will take as much time to upgrade as it takes time to upgrade. Its only warning is especially in 1.4 upgrades, added JSON hardness:
jQuery 1.3 and used JavaScript Eval to evaluate the incoming JSON first. JQuery 1.4 uses the original JSON parser if available. It validates incoming JSOS for validity, so Jasonson (for example,
{foo: "bar"}) will be rejected by JAX and when an AJAX request to "Jason" Will be referred to as datatype. / P>
This means JSON operations too is fast, but old / invalid JSON will not cut it. If they have to fix web-services, because JSON should be absolutely valid in 1.4+, this can be a show-stop on a upgrade for a big project ... and I'm not sure what you have to say. .
As plugins ... every major / popular plugin supports the new release very quickly, if not, they are very fast to fix themselves ... and many people have some Editing is also not required because they were not broken by upgrades (however, check out the new version of the plugin, they can increase performance by a new version of the core).
Comments
Post a Comment