|
FAST Protocol
< Previous Next >
Re: FAST too complex?
Anders Furuhed / Pantor Engineering 9 Jan 2009 7:28AM ET >
> IMHO the quality of a protocol specification can be determined from how
> many questions people ask about it ?., the fewer the questions the less
> ambiguous the specification is. You only have to look in these forums to
> see the number and variety of problems. If you can write a spec, send it
> to a developer in Australia and he/she can decode your data without
> needing to contact you for clarification, then the specification is very
> high quality.
>
One of David's main goals prompting him to write the document that became the 1.1 spec was to remove the ambiguity that he saw in the 1.0 days. A tutorial was intentionally left outside the core document (and has yet to materialize).
If the spec is ambiguous by e.g. leaving out details or using language that is open to interpretation, that is a problem that should be addressed with an update to the document.
Let's distinguish between the document being a non-ambiguous specification or not (can someone in Australia get an implementation right with only the specification document available) and the need for a tutorial and/or a reference implementation that would make life much easier for implementors. I'm not saying the latter is not important.
Yes William Hooper / NA 23 Dec 2008 8:30AM ET Re: Yes Rolf Andersson / Pantor Engineering 23 Dec 2008 9:49AM ET Re: Yes William Hooper / NA 24 Dec 2008 10:30AM ET Re: Yes Rolf Andersson / Pantor Engineering 24 Dec 2008 2:14PM ET Re: Yes Clive Browning / Rapid Addition Ltd 24 Dec 2008 4:52PM ET Re: Yes Ravi Ravisankar / IBM 23 Dec 2008 8:55PM ET Re: Yes Rolf Andersson / Pantor Engineering 24 Dec 2008 12:59AM ET Re: Yes Ravi Ravisankar / IBM 25 Dec 2008 9:39PM ET Re: Yes Hanno Klein / Deutsche Börse Systems 28 Jan 2009 5:37AM ET Re: Yes William Hooper / NA 24 Dec 2008 10:46AM ET Re: Yes Rufus Me / Self 28 Dec 2008 8:43PM ET Re: FAST too complex? Anders Furuhed / Pantor Engineering 9 Jan 2009 7:28AM ET |