|
FAST Protocol
< Previous Next >
Re: Reinventing Text and NICs
Daniel May / SpryWare, LLC <>
22 Jul 2008 10:12PM ET You are missing the point, again read the proof of concept and original design goals, specifically
http://fixprotocol.org/documents/2300/LSE%20Presentations.zip
There were several design constraints that we had to adhere to, and multiple proposed solutions were evaluated before we settled on FAST. Your focus on a hardware based, NIC solution is very short sighted. There are far too many transport and media formats to consider.
How can you say the reduction of bandwidth by over 70% in most cases is not a valid proof of concept ? Yes, data elimination is always a better way of reducing bandwidth than data compression, but we can not dictate what an exchange or vendor can or cannot include in a data feed.
And what is with all the secrecy ? Retired from where ? What exchanges have dropped FAST ?
> If you can provide a set of samples, I will provide proof FAST does
> not gain anything more than 3% over existing methods done in hardware
> and very little work done in app-level space. And that 3% will come at
> a huge cost that can be put to better use elsewhere.
The sample data is on the FAST web site, but you already know that since you have read all the information available.
I eagerly await your results.
Anyway, I do not think your comments really warrant any more of my time. Your motive is an ulterior one, I am just not sure what yet.
/Daniel
Re: Reinventing Text and NICs
Daniel May / SpryWare, LLC 22 Jul 2008 10:12PM ET
|
@FIXProtocol
