Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

how to use userData when async send callback called? #192

Closed
ShannonDing opened this issue Sep 25, 2019 · 2 comments
Closed

how to use userData when async send callback called? #192

ShannonDing opened this issue Sep 25, 2019 · 2 comments
Labels
enhancement New feature or request
Milestone
1.2.4

Comments

@ShannonDing
Copy link
Member

FEATURE REQUEST

  1. Please describe the feature you are requesting.
    it is better for async send back to support userdata
  2. Provide any additional detail on your proposed use case for this feature.
    typedef void (*COnSendSuccessCallback)(CSendResult result, CMessage *msg, void *userData);
    typedef void (*COnSendExceptionCallback)(CMQException e, CMessage *msg, void *userData);
  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
    should-have
  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
@ShannonDing ShannonDing added the enhancement New feature or request label Sep 25, 2019
@ShannonDing ShannonDing added this to the 1.2.4 milestone Sep 25, 2019
@francisoliverlee
Copy link
Member

FEATURE REQUEST

  1. Please describe the feature you are requesting.
    it is better for async send back to support userdata
  2. Provide any additional detail on your proposed use case for this feature.
    typedef void (*COnSendSuccessCallback)(CSendResult result, CMessage *msg, void *userData);
    typedef void (*COnSendExceptionCallback)(CMQException e, CMessage *msg, void *userData);
  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
    should-have
  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

specially for py-client to callback, can not know which message send ok for py client

@ShannonDing
Copy link
Member Author

reffer to #193

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
1.2.4
Development

No branches or pull requests
2 participants
@francisoliverlee @ShannonDing