Sean Feldman

@RussKie glad you brought that up. I'd rather focus on functionality and not worry about reuse. Reuse can cause abuse 😉 I haven't looked at the code yet to provide...

> How does that sound? Sounds good. Will take a stab at it this week.

Sorry for delay. I've actually found templates to be very helpful. I've defined one of the templates, as a `Co-authored` template and use it when pairing.

If multiple queues need to be processed by a single processor (Azure Functions in this case), look at Azure Service Bus and the [Auto-forwarding feature](https://www.serverless360.com/blog/auto-forwarding-a-hidden-gem-of-service-bus). The feature was designed years...

> That's ignoring the purely philosophical issue of your infrastructure having to be altered and managed because of a product deficiency that could be rather easily addressed. Please share details...

@Simon-Gregory-LG, Given that ASB doesn't support priority queues, I'm not sure how you expect Functions to come up with that feature without inventing something it's not designed to do.

ASB Functions trigger (queue or subscription) is based on the Processor from the SDK. It works with long polling of a single entity. Assuming the team would abandon that implementation...

> Btw does the queue trigger actually use long polling? Yes, it does.

> Are you talking about service bus or azure storage Queues? I have been [explicitly](https://github.com/Azure/azure-webjobs-sdk/issues/808#issuecomment-1931337297) talking about Azure Service Bus (ASB). Storage Queues are handy but their share in the...

The original request is from 2016. Even back then, ASQ was already in the back mirror. Some systems still use it. It's a very simple queuing service to start with,...