Open mteper opened 8 years ago
As I mentioned in your other issue, we're trying to be very conservative with our public surface area. We want to make sure that any new public surface area that we open up will stand the test of time, so we've consciously only opened up the bare minimum required to allow people to plug in. Our plan is to look at all the extensions people want to write and extract patterns / interfaces that are clean and make sense from them, so we're confident that what we expose as a foundation is clean and can stand the test of time :) Many of the core bindings we have in the SDK now might be overly complicated, which is why we haven't taken the approach of just flipping the switch and making everything public. We want to make sure that we expose a platform that is as simple as possible for people. In the short term that might mean that your job is harder of course.
The entire extensibility model is under active development, and we value your feedback.
@mathewc I appreciate that, and I also agree that SDK internals feel, if not over-engineered, then definitely mindbendingly complex. That said, the classes in Timers namespace, TimeSeriesTimer
among them, feel quite fundamental to me. I would suggest that these might be first in queue to open up for reuse.
I think we'll go ahead and backlog this for now. We have no plans to open up a complex thing like TaskSeriesTimer
in the immediate future.
I am writing an binding / trigger extension for AWS SWF, loosely modeling my code on the Azure Storage Queues implementation, and it would be very helpful to have access to
TaskSeriesTimer
and related classes.