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

Split client and server from parsing #231

Closed
insomniacslk opened this issue Jan 18, 2019 · 2 comments
Closed

Split client and server from parsing #231

insomniacslk opened this issue Jan 18, 2019 · 2 comments

Comments

@insomniacslk
Copy link
Owner

This will allow finer-grained imports for who only needs a subset of the functionalities (e.g. no need for server or client)
@insomniacslk insomniacslk mentioned this issue Jan 18, 2019
Closed
@hugelgupf
Copy link
Collaborator

+1

@begetan begetan mentioned this issue Jan 27, 2019
Closed
@insomniacslk
Copy link
Owner Author

As @hugelgupf suggested offline, I will split as follows:

  • dhcpv6/client6
  • dhcpv4/client4
  • dhcpv6/server6
  • dhcpv4/server4

To be decided what to do with the async clients (currently dhcpv6/async and dhcpv4/async)

@insomniacslk insomniacslk mentioned this issue Jan 27, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hugelgupf @insomniacslk