Why do we have a cumbersome system of handles for time and sales and bar data.
Nobody will ever want to receive twice the same symbol. Give me a situation where somebody would want to subscribe twice to the same symbol knowing how quick the active x gets clogged.
This design of handles is not adapted to our problem.
This said I have nothing against an integer to identify the incoming flow but I think two modifications make sense:
- Exception thrown when the user ask for a new handle on an already subscribed symbol.
- possibility of specifying ourself the handles, would be nice to associate a position in the array and a symbol.
I understand it's a big change... at least could you provide us with a function that return a list of the handles opened and the symbol associated.
I already see a response coming back, such as if you code well you will never have two handle on the same symbol...
Thanks,
Nick.
Nobody will ever want to receive twice the same symbol. Give me a situation where somebody would want to subscribe twice to the same symbol knowing how quick the active x gets clogged.
This design of handles is not adapted to our problem.
This said I have nothing against an integer to identify the incoming flow but I think two modifications make sense:
- Exception thrown when the user ask for a new handle on an already subscribed symbol.
- possibility of specifying ourself the handles, would be nice to associate a position in the array and a symbol.
I understand it's a big change... at least could you provide us with a function that return a list of the handles opened and the symbol associated.
I already see a response coming back, such as if you code well you will never have two handle on the same symbol...
Thanks,
Nick.
Comment