08-24-2010, 07:17 PM
|
#1 |
Join Date: Jan 2007 Location: USA Thanks: 1,912
Thanked 1,789 Times in 895 Posts
| OEC Stops Explained Since there's at least one person giving inaccurate information on how OEC handles stops, I emailed my OEC contact asking for clarification on how stops work. From the source: If the exchange supports stops/stop limits (for the given product) OEC sends those to the exchange.
The only stops we would hold on our servers would be:
1. Synthetic stops (ie trailing stops). And this implementation is pretty good as many platforms do these client side.
2. Multi-legged brackets (“Strategy Order” (Thumbs up) on the DOM ). These work client side.
3. The exchange may not support stops (natively), so OEC may synthetically create a stop order for the client on our server. If someone places a stop in the DOM, if the exchange supports it for that contract, it goes to the exchange. Contrary to what you may have heard from others on this very site, that is how stops are handled. In a nutshell, if you place your stop on the DOM and the exchange supports stops, it's at the exchange. Now if the exchange does not support it, then there's not much OEC can do at that point but I'm sure there's a couple here that will find fault with that as well.
Just another example of why you should contact your broker directly (regardless of who the broker is) and get the answer yourself. While forums are nice, there's plenty of misinformation presented either due to lack of knowledge or wanting to put down a broker for the sake of putting them down. |
| |