|
FAST Protocol
< Previous Next >
Questioning support for Type Conversion
Jim Northey / Jordan and Jordan
10 Apr 2006 3:47PM ETDuring my initial review of the FAST Template Definition (TD) Speciifcation - the specification of type conversion is one point that I really felt was embellishment and should not be part of the FAST Protocol and should be omitted. This is better left to implementors.
There is a difference between an API and a library layer of convenience functions and presentation services. I believe we should stay below these levels and omit this practice.
Also, FAST is a message protocol, and while it does have datatypes, it does not have the demands for type conversion/coercion implicit or otherwise as that of a programming language.
I would also point out that type safety and coercion / conversion rules are a rife area for philosophical debate within computer science, and as such I would like to exclude this layer and these arguments as being of diminished value for the application of our very limited time in specification creation and maintenance.
With that said, I also think I am one of the less capable folks in this discussion – so I would like some feedback and justification if others feel strongly that we should expand the scope of the FAST specification to include type conversion / coercion.
Questioning support for Type Conversion
Jim Northey / Jordan and Jordan 10 Apr 2006 3:47PM ET
|
