Tom Igoe

I like the look of that stub. The examples are very clear and useful.

What would you call that class, Paul? I can see some sense in the idea, and I'm curious whether the name should reflect processor type or something else. For example,...

That clears things up, thanks. PowerManager is pretty good as a name, I could go with that.

Another advantage to the static class is that it makes for clearer differentiation between Processor sleep and peripheral sleep, for example the wifi sleep on the MKR1000. In fact, it...

+1 that. Don would have good feedback.

A couple thoughts: 1. Yes, work toward shorter class names. How much overlap is there between the central and peripheral libraries, and can they share any common transport or config...

I think the local/remote thing is confusing. We don't distinguish between local/remote clients with the client/server libraries in WiFi, do we? Maybe the same principle should apply here. "However, it...

+1 to all that. glad we're on the same page.

Are these breaking changes going to be back-ported to BLE-Peripheral? I would recommend doing so in the interests of compatibility.

In the central sensorTag application, why don't you have to check that the characteristic exists before you subscribe to it?