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.

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

DISPATCH-557 - Moved management of connections from python agent to r… #125

Closed
wants to merge 1 commit into from

Conversation

ganeshmurthy
Copy link
Contributor

…outer core

@@ -23,6 +23,7 @@
#include <qpid/dispatch/bitmask.h>
#include <qpid/dispatch/compose.h>
#include <qpid/dispatch/parse.h>
typedef struct qdr_core_t qdr_core_t;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move this back down with the other typedefs. You can add this line into router.h to solve the compilation issue.

break;

case QDR_CONNECTION_SASL_MECHANISMS:
qd_compose_insert_string(body, conn->connection_info->sasl_mechanisms);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sasl_mechanisms is 0 if not specified. That causes a crash here (easily reproducible by starting the web console). If it's not present, this should insert a NULL into the body.

bool is_authenticated,
bool opened,
char *sasl_mechanisms,
const char *dir,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an enumerated type for direction. You should use this rather than passing strings around.

char *user;
bool is_authenticated;
bool opened;
const char *dir;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think dir and role should use the enumerated types rather than arbitrary strings.

@ganeshmurthy ganeshmurthy deleted the DISPATCH-557-2 branch July 5, 2017 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants