Queues changes |
|
Description |
The Service Bus Queues feature has been changed due to customer feedback and is renamed to “Message Buffer” in order to better reflect the associated capabilities. Message Buffers will be introduced with temporary caching functionality in the November 2009 CTP and the long term goal of providing comparable functionality to queues. |
|
Pre-Release Behavior |
Queues provide persistent message storage. Microsoft.ServicesBus.dll provides APIs such as QueueClient, QueueManagementClient, QueuePolicy for interaction with Queues |
|
Post-Release Behavior |
Message Buffers provide message caching. Queues related APIs will be removed from Microsoft.ServicesBus.dll. MessageBufferClient APIs will be provided in Microsoft.ServicesBus.dll for interaction with the new Message Buffers |
|
Recommended Post-Release Action |
References to Queues should be removed from applications. For some applications, Message Buffers may be substituted for Queues. Where durability requirements exist, solutions employing Azure storage features may be preferred. |
Routers removal |
|
Description |
Service Bus Routers feature will be removed. A November 2009 CTP sample will be provided to demonstrate how to implement an ‘anycast’ message distribution model similar to the Router’s respective capability |
|
Pre-Release Behavior |
Routers push messages to a subscription list. Microsoft.ServicesBus.dll provides APIs such as RouterClient, RouterManagementClient, RouterPolicy etc… for interaction with Routers |
|
Post-Release Behavior |
Routers functionality as well as related Microsoft.ServiceBus.Router APIs are removed |
|
Recommended Post-Release Action |
Router API calls should be removed from applications. For some applications, the approach suggested in the LoadBalance sample may provide sufficient message routing functionality. Other approaches are possible but are likely to require more client code. |
RelayBinding Security Default |
|
Description |
All RelayBindings are secured by default in the November 2009 CTP |
|
Pre-Release Behavior |
Some RelayBindings have RelaySecurity.Mode set to EndToEndSecurityMode.None |
|
Post-Release Behavior |
All RelayBindings have RelaySecurity.Mode set to EndToEndSecurityMode.Transport which is secured by default |
|
Recommended Post-Release Action |
User code using any RelayBinding should be updated to use HTTPS transport in service and endpoint addresses. As an alternative, the RelayBinding RelaySeucirty.Mode can be set to EndToEndSecurityMode.None. Note that setting EndToEndSecurityMode.None allows message contents to travel in clear text, considered a security risk for many applications |
Service Namespace replaces Solution name |
|
Description |
Solution name is replaced as Service Namespace in the November 2009 CTP |
|
Pre-Release Behavior |
Solution is the basic naming for a .NET Services solution i.e. http://<solution>.servicebus.windows.net |
|
Post-Release Behavior |
Service Namespace is the basic naming for a .NET Services application i.e.
http://<service_namespace>.servicebus.
windows.net |
TransportClientCredentialType update |
|
Description |
TransportClientCredentialType such as AutomaticRenewal, CardSpace, ClientCertificate, FederationViaCardSpace and UserName will be removed in the November 2009 CTP release. They will be replaced by credential types that are supported by the new Access Control Service |
|
Pre-Release Behavior |
Service Bus authentication type includes CardSpace, X509Certificate, FederationViaCardSpace and UserNamePassword and are reflected in TransportClientCredentialType |
|
Post-Release Behavior |
Service Bus authenticated type includes SharedSecret, Simple Web Tokens and Saml which are reflected in TransportClientCredentialType |
|
Recommended Post-Release Action |
User code using TransportClientCredentialType in the July 2009 CTP should be updated to use the authentication types employed in the November 2009 CTP.. Sample code will be provided in the November 2009 CTP SDK to illustrate how to use the new authentication type |
EndToEndWebHttpSecurityMode.
TransportCredentialOnly is removed |
|
Description |
EndToEndWebHttpSecurityMode.
TransportCredentialOnly is removed |
|
Pre-Release Behavior |
EndToEndWebHttpSecurityMode.
TransportCredentialOnly option exists |
|
Post-Release Behavior |
EndToEndWebHttpSecurityMode.
TransportCredentialOnly option is removed as it is not supported |
|
Recommended Post-Release Action |
User code using EndToEndWebHttpSecurityMode.
TransportCredentialOnly should use EndToEndWebHttpSecurityMode.Transport instead |
HttpBufferClient is not public |
|
Description |
Microsoft.ServiceBus.HttpBufferClient is removed from public APIs |
|
Pre-Release Behavior |
Microsoft.ServiceBus.HttpBufferClient is public |
|
Post-Release Behavior |
Microsoft.ServiceBus.HttpBufferClient is no longer public |
|
Recommended Post-Release Action |
User code using HttpBufferClient may be replaced by MessageBufferClient |
TcpRelayConnectionMode.Direct is removed |
|
Description |
Microsoft.ServiceBus.
TcpRelayConnectionMode.Direct is removed |
|
Pre-Release Behavior |
Microsoft.ServiceBus.
TcpRelayConnectionMode.Direct exists |
|
Post-Release Behavior |
Microsoft.ServiceBus.
TcpRelayConnectionMode.Direct is not supported; Direct Connection is supported in Hybrid mode only. |
|
Recommended Post-Release Action |
User code using TcpRelayConnectionMode.Direct may be replaced by TcpRelayConnectionMode.Relayed or TcpRelayConnectionMode.Hybrid |
Service publishing feed address aligns with service transport |
|
Description |
Service publishing feed address aligns with service transport |
|
Pre-Release Behavior |
Service publishing feed address used HTTP transport i.e. http://<mysolution>.servicebus.windows.net/
<mycalculatorservice> regardless of the transport being used in the service i.e. service is accessed at “sb://<mysolution>.servicebus.windows.net/
<mycalculatorservice>” when NetTcpRelayBinding is used |
|
Post-Release Behavior |
Service publishing feed address is now aligned with the service transport i.e. the feed will be accessed at “sb://<mysolution>.servicebus.windows.net/
<mycalculatorservice>” when service is accessed at “sb://<mysolution>.servicebus.windows.net/
<mycalculatorservice>” |
|
Recommended Post-Release Action |
User code referencing service publishing feed address may be updated with matching service transport |
WSHttpRelayBinding is removed |
|
Description |
WSHttpRelayBinding is no longer supported |
|
Pre-Release Behavior |
WSHttpRelayBinding is supported |
|
Post-Release Behavior |
WSHttpRelayBinding is no longer supported |
|
Recommended Post-Release Action |
User code using WSHttpRelayBinding should be changed to use another supported binding such as WS2007HttpRelayBinding or user-constructed custom binding |
WS2007FederationHttpRelayBinding is removed |
|
Description |
WS2007FederationHttpRelayBinding is no longer supported |
|
Pre-Release Behavior |
WS2007FederationHttpRelayBinding is supported |
|
Post-Release Behavior |
WS2007FederationHttpRelayBinding is no longer supported |
|
Recommended Post-Release Action |
User code using WS2007FederationHttpRelayBinding should be changed to use another supported binding such as WS2007HttpRelayBinding or user-constructed custom binding |
