|
FAST Protocol
< Previous Next >
Re: Improving FAST
Dale Wilson / Object Computing, Inc
25 Feb 2010 12:34PM ET > the extensibility mechanism in FAST 1.1 can be used to specify maximum
> lengths etc. Please refer to section 9.
Agreed, but because the length issue is not explicitly addressed in the specification, exchanges (template authors) may not think of it or may be reluctant to add custom extensions.
Even if they did, there's nothing leading different exchanges to choose the same name for the extension attribute: (capacity, size, upper_bound, length, max_length, ...) so I'm still stuck with writing custom adapters for different data feeds.
Of course all the market data sources could join together and choose a single name for the max-string-length and max-sequence-length attributes, but such an agreement seems to me to be exactly what the specification is there for in the first place.
The real question is, is this an important enough issue that it should be addressed in future versions of the specification. To me it seems like it is, but other opinions may vary. FAST works OK without this feature, but I think it would be better if the issue were addressed.
Dale
PS: As one example of this issue being addressed in another standard, CORBA allows the definition of bounded and unbounded strings in IDL:
attribute string name;
is unbounded
attribute string[10] serial_number;
has a maximum length of 10 characters.
(subbing square brackets for angle brackets to make the message archives happy)
Improving FAST Dale Wilson / Object Computing, Inc 29 Jan 2010 11:09AM ET Re: Improving FAST
Dale Wilson / Object Computing, Inc 25 Feb 2010 12:34PM ET
|
