Imported from previous forum
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
In FIX 4.2, Market Data Request, Security Status Request, Trading Session Status Request permit enabling disabling subscription using the SubscriptionRequestType[263] field.
We are getting requests from users for an application level acknowledgement when a subscription is disabled. At this point in time the lack of an acknowledgement is assumed to indicate that the request was handled.
Does anyone else think we should provide application level acknowledgement to requests to disable subscriptions?
> We are getting requests from users for an application level acknowledgement when a subscription is disabled. At this point in time the lack of an acknowledgement is assumed to indicate that the request was handled.
What is the acknowledgment supposed to indicate? That (a) the subscription cancel was received and will be processed, or (b) it follows the last update as a guarantee no more will follow.
It seems to me that:
type (a) offers little benefit since the FIX session protocol essentially guarantees delivery (and a test request can prove it)
type (b) might simplify client code for freeing resources, but could prove awkward and/or inefficient for an asynchronous publishing engine to generate.
What are the arguments submitted in favour of the change?
Cheers, Dave