This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 370
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #9 from veena-udayabhanu/master
XSCL Hotfix 3.0.1
- Loading branch information
Showing
40 changed files
with
336 additions
and
115 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,39 +1,44 @@ | ||
Tracking changes for all breaks since 2.0 | ||
|
||
- Auth Handlers were delay populated in 2.0. They are now going to be populated in the client constructors. They are internally settable. So Test can change it. | ||
Tracking Breaking Changes since 2.0 | ||
|
||
- maxResults while listing queues in nullable now. | ||
|
||
- Table now allows query execution with a resolver against non generic query types(Dynamic Entity types). | ||
- The BlobTypeMismatch and ExtendedErrorUnavailable error strings have changed in SR.cs. | ||
|
||
- Container, Blob, Directory, Queue and Table names are now validated at the client side. | ||
- OperationContext.RequestResults does not expose a setter anymore. | ||
|
||
- Table now does SAS similar to queues and containers. | ||
- Renamed CloudQueue.EndBeginClear(IAsyncResult) to CloudQueue.EndClear(IAsyncResult). | ||
|
||
- All header, query and generic constants are public now so people can use it when they use protocol layer. | ||
- StreamExtensions.WriteToSync<T>(Stream, Stream, long?, long? bool, bool, ExecutionState<T>, StreamDescriptor) now throws InvalidOperationException(SR.StreamLengthError) instead of ArgumentOutOfRangeException("stream"). | ||
|
||
- There is now a way users can update their sastoken. This is provided by the StorageCredentials class' updateSas method. | ||
- StreamExtensions.WriteToAsync<T>(stream, Stream, long?, long?, bool, ExecutionState<T>, StreamDescriptor, CancellationToken token) now throws InvalidOperationException(SR.StreamLengthError) instead of ArgumentOutOfRangeException("stream"). | ||
|
||
- Users now have an API that takes only the key value when they want to update their key. | ||
- The StorageException thrown when an operation is cancelled now includes an OperationCanceledException as its inner exception. | ||
|
||
- Cloud*Blob now has BeginOpenRead and EndOpenRead methods to asynchronously open a stream to read from the blob. | ||
Tracking Breaking Changes since 2.1 RTM | ||
|
||
- The BlobTypeMismatch and ExtendedErrorUnavailable error strings have changed in SR.cs. | ||
- When DataServiceContext is used to execute table operations, response received event on OperationContext is no longer fired. | ||
|
||
- OperationContext.RequestResults does not have a setter anymore. | ||
- ContinuationTokens are written with an additional <ContinuationToken> element enclosing them if WriteXml() method is used - ReadXml() parser is updated to handle this. | ||
|
||
- Renamed CloudQueue.EndBeginClear(IAsyncResult) to CloudQueue.EndClear(IAsyncResult). | ||
- Only the ServiceProperties that are provided are changed. In previous REST versions ommitting a properties section such as Metrics would result in those settings being removed by the service. | ||
|
||
- StreamExtensions.WriteToSync<T>(Stream, Stream, long?, long? bool, bool, ExecutionState<T>, StreamDescriptor) now throws InvalidOperationException(SR.StreamLengthError) instead of ArgumentOutOfRangeException("stream"). | ||
- Please refer to the blog post about Breaking Changes on the server side in the new storage protocol version(2013-08-15) here: | ||
http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/23/windows-azure-storage-breaking-changes-for-windows-azure-tables-november-2013.aspx. | ||
|
||
- StreamExtensions.WriteToAsync<T>(stream, Stream, long?, long?, bool, ExecutionState<T>, StreamDescriptor, CancellationToken token) now throws InvalidOperationException(SR.StreamLengthError) instead of ArgumentOutOfRangeException("stream"). | ||
Additionally, the following error messages have changed in the Table Service: | ||
|
||
- The StorageException thrown when an operation is cancelled now includes an OperationCanceledException as its inner exception. | ||
Entity over 1MB � | ||
|
||
Tracking changes for all breaks since 2.1 RTM | ||
Error message previously - The entity is larger than allowed by the Table Service. | ||
Error message now - The entity is larger than the maximum allowed size (1MB). | ||
|
||
- When DataServiceContext is used to execute table operations, response received event on OperationContext is no longer fired. | ||
Batch over 4MB - | ||
|
||
Error message previously - The content length for the requested operation has exceeded the limit. | ||
Error message now - The content length for the requested operation has exceeded the limit (4MB). | ||
|
||
Property name over 255 chars � | ||
|
||
- ContinuationTokens are written with an additional <ContinuationToken> element enclosing them if WriteXml() method is used - ReadXml() parser is updated to handle this, but anyone parsing their own could be affected | ||
Error message previously � The property name exceeds the maximum allowed length. | ||
Error message now - The property name exceeds the maximum allowed length (255). | ||
|
||
- Only the ServiceProperties that are uploaded are changed. For example, if the user wants to just set CORS, the Logging and Metering related settings elements can be omitted and the omitted settings will be remain unchanged. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.