projectextensions/projectextensions.azure.servicebus

ProjectExtensions.Azure.ServiceBus

projectextensions.azure.servicebus's Issues

Deal with IDisposable message handlers that are per-instance

Per-instance message handlers could also implement IDisposable. If they do, they have to be "released" when we are done with them. This is not the same as calling dispose directly (at least for most containers). Most IoC containers have some concept of Release. For example, Castle Windsor has an explicit release method. Some IoC container have the concept of a sub-container that calls IDispose for its components when it goes out of scope. This does have to be handled because, for at least Castle Windsor, this can cause memory leaks because in some cases the IoC container will hold onto the reference until the component is released or until the container itself is disposed.

Implement commonservicelocator

http://commonservicelocator.codeplex.com/

Document what to do if you can't deal with a message

Strong Name the NuGet package

I would like to use your library, but my assemblies use strong name keys.

Document Async and speed of it and why you should use it

Add ability to change the filter on a subscription

Not sure if we have to update to v2 of the lib or not.

Add support for Handler throttling for after errors.

Right now if there is an error with the handler, we retry right away. We want to be able to pause for a period of time.

Document TopicName and provide examples

There is no reference to what topic name is and why you would use it.

Add support for Service Bus for Windows Server

Would be nice to be able to use this lib with Service Bus for Windows Server so that you are not forced to have account on azure. The development will be much simplified in this case.

Move metadata to interface and remove second parameter from call.

public void Handle(IReceivedMessage message, IDictionary<string, object> metadata)

will become

public void Handle(IReceivedMessage message)

and message will have a new metadata property.

Correlation Filter and Properties

I did not write down details :(

Send Batch Support

We do not support the transaction ability of send

Add support to verify if a subscriber exists

Supported in the new api

Document MessageHandlerConfiguration

Need information to describe the custom attribute.

Determine why Create Topic takes many minutes

ExecuteAction in AzureBusReceiver takes a long time if the item does not exist.

Add new property DeadLetterAfterMaxRetries to Config

This will dead letter the message and never call the receiver after the max retries is reached.

Support Scheduled Enqueue Time

Needs to be part of the sent message or a param?

Support RenewLock and LockUntil

Determine how we can pass that back or add a property on the message so we can renew the lock past the default 2 minutes.

ReadFromConfigFile must read azure config if running in Azure

See subject. Right now it only ready the app.config file.

Add ability to provide additional filters to the subscription

Right now we filter only on the type. We need to be able to add additional filters based on headers in the message.

We may just provide A collection of Filter and let people set their own.

Document IHandleCompetingMessage<T> compared to IHandleMessage<T>

Explain why by default we look at the fully qualified class name to determine if you are scaling out or of you are creating a new subscription.

Limit number of async calls that are in flight

People will now know that if you call PublishAsync 1000 times in a loop that tons of threads are being produced. We need to set a default number of senders and then have those senders poll the queue.

Deal with throttle exceptions

ProjectExtensions.Azure.ServiceBus.Sender.AzureBusSender 24 09:18:23 Send failed Microsoft.ServiceBus.Messaging.ServerBusyException: The request was terminated because the entity is being throttled. Please wait 10 seconds and try again..TrackingId:e99587b8-46ba-4ef3-a386-ba15f8761523_G20_B12,TimeStamp:3/24/2013 1:18:24 PM ---> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: The request was terminated because the entity is being throttled. Please wait 10 seconds and try again..TrackingId:e99587b8-46ba-4ef3-a386-ba15f8761523_G20_B12,TimeStamp:3/24/2013 1:18:24 PM

Allow for multiple Topics.

We would need to add TopicName to the Configuration data. If it is not configured then it would use the default created when the application was configured.

Document AppName and the purpose of it

There is no explanation of AppName. Describe it and why you need it if you are using the same topic for multiple applications.

Remove singleton attribute and put property in config

Deprecate the attribute and place singleton property into the config attribute.

Remove AzureConfigurationHelper

PublishAsync auth causes Task Exception

See email stack trace. Only happened once.

Implement DeadLetterAfterMaxRetries polling for a subscription.

We place the message in the DeadLetterQueue but we do not provide a way to obtain the information from that Queue.

Verify we documented the WithSettings Change

Recreate a subscription if it is deleted.

If a subscription endpoint is deleted the application throws errors. Recreate it on demand.

Create wiki Getting Started page that includes images from the Azure Portal

Create a step by step example to get people started with the service bus including the new azure portal.