-
Notifications
You must be signed in to change notification settings - Fork 4
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
Should we rename XService classes to XEndpoint? #19
Comments
The original idea was to be roughly following the architecture of libpebble2 (https://github.com/pebble-dev/libpebble2/tree/master/libpebble2/services) but it might not be appropriate naming for how we want to use them |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, all communication classes are named
MusicService
,SystemService
etc., but they are not really services. They only facilitate communication between watch and phone.I suggest that we rename those to the
MusicEndpoint
,SystemEndpoint
etc. That way we can createMusicService
in the app without naming conflicts.@crc-32 what do you think?
The text was updated successfully, but these errors were encountered: