|
4.1 Changes
< Previous Next >
re: ID Changes
Val Melamed
6 Feb 1998 7:53PM ETI agree with Mark and Scott on this topic. It is not that simple to *just* change the type and to generalize for the previous versions. Even if it is guarateed that no site will ever send alphanumeric IOIRefId to FIX.2.7, 3.0, 4.0 sites, here is what "just changing the type" would mean for us:
1) change of data base column types;
2) change of data base stored procedures;
3) loosing some perfomance in the searches (char[n] vs. int) both in the DB and in the code (ok, I can leave with this... :) );
4) many changes of the back end and front end code;
5) upgrading lots of cusmers.
Currently only we have installed over 30 servers talking FIX 2.7, 3.0, 4.0 and respectively 30*N client programs.
I really don't know what exactly requires the change of the types of all these fields, but I am strongly opposed to it, unless someone out there proves that there is a very good compeling reason. In such a case, I would agree with Mark and Scott -- let's have new fields.
Please, guys, think about the fact that the most of the FIX sites are still talking 3.0. Putnam is still using 2.7...
Val
Ease Technolgies
re: ID Changes
Val Melamed 6 Feb 1998 7:53PM ET
|
