search

TheThingsArchive / java-app-sdk

The Things Network Application SDK for Java
MIT License
30 stars 25 forks source link

Implement Gateway & Component management #42

Closed cambierr closed 7 years ago

FokkeZB commented 7 years ago

Although I welcome this, it does expand the SDK beyond the current "app" scope. What would you suggest @johanstokking?

johanstokking commented 7 years ago

Yes, I can imagine it's very welcome but indeed this is beyond the application scope.

The application scope, on a high level, interfaces with the Handler through the Application Manager and Data API, and uses the Account Server for authentication. Gateway and component management is resource management on the Account Server.

I'd suggest introducing a new repository for this. Not sure what's common in the Java ecosystem though.

cambierr commented 7 years ago

Well, since it's related to account, my opinion is that we could include this in the account library.

Then, we should rename this repo into something like java-sdk and just drop "app" ?

When building the project, all artifacts will be separated anyway and individually releasable, even if sitting in the same git repo.

johanstokking commented 7 years ago

OK sounds good

FokkeZB commented 7 years ago

I guess how we deal with this also depends on the language and options to separate different parts of the SDK to keep it lightweight. For example, for Nodejs I'd suggest splitting it into ttn-data, ttn-account etc with ttn depending on all of them. Much like lodash, allowing you to also just depend on what you need instead of the all in one.