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

Improve code organization #376

Closed
bgrainger opened this issue Oct 22, 2017 · 1 comment
Closed

Improve code organization #376

bgrainger opened this issue Oct 22, 2017 · 1 comment
Assignees

Comments

@bgrainger
Copy link
Member

@bgrainger bgrainger commented Oct 22, 2017

The current code layout has evolved in a somewhat haphazard way. To make it more internally consistent and easier for new contributors to get involved, I propose reorganising it as follows:

  • MySqlConnector
    • MySql.Data.MySqlClient - only types necessary to clone Connector/NET public API
    • Protocol - enums, constants, etc. defined in the MySQL protocol
      • Payloads - types representing individual payloads
      • Serialization - reading/writing packets & payloads
    • ? - ADO.NET implementation helpers, MySqlSession, MySqlParser, MySqlXaTransaction, etc.
    • Utility - general-purpose code, extension methods
@bgrainger bgrainger self-assigned this Oct 22, 2017
@bgrainger
Copy link
Member Author

@bgrainger bgrainger commented Oct 24, 2017

It would be good if the reorganisation could make it easier to expose a "direct" API (that corresponds much more closely to the underlying MySQL protocol) for clients who need high-performance access but don't need/want ADO.NET.

bgrainger added a commit that referenced this issue Nov 8, 2017
Improve internal code organisation. Fixes #376
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant