Issue 486 in tradelink: add option to TLTracker to disable reconnections when no ticks have arrived yet

[trad...@googlecode.com]

Status: Accepted
Owner: frantajosh
Labels: Type-Enhancement

New issue 486 by frantajosh: add option to TLTracker to disable
reconnections when no ticks have arrived yet
http://code.google.com/p/tradelink/issues/detail?id=486

this is useful for situations when no symbols have been subscribed yet.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[trad...@googlecode.com]

Comment #1 on issue 486 by frantajosh: add option to TLTracker to disable

reconnections when no ticks have arrived yet
http://code.google.com/p/tradelink/issues/detail?id=486

probably should also expose the Reconnect method to public so users can
manually
request a new connection in this event.

[trad...@googlecode.com]

Comment #2 on issue 486 by frantajosh: add option to TLTracker to disable

reconnections when no ticks have arrived yet
http://code.google.com/p/tradelink/issues/detail?id=486

I think in this event, we might also want to add SERVERUP/SERVERDOWN
messages to
TLServer whenenever a connector is started up or closed (resp).

this would be sent as a broadcast, and clients would be able to catch it
which would
handle clean startups and exits better.

NativeMethods.PostMessage(
(IntPtr)NativeMethods.HWND_BROADCAST,
NativeMethods.WM_SHOWME,
IntPtr.Zero,
IntPtr.Zero);

[trad...@googlecode.com]

Updates:
Status: Verified

Comment #3 on issue 486 by frantajosh: add option to TLTracker to disable

reconnections when no ticks have arrived yet
http://code.google.com/p/tradelink/issues/detail?id=486

r1736

opened another ticket for broadcast feature