Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Azure: Enterprise Application Development

You're reading from   Microsoft Azure: Enterprise Application Development Straight talking advice on how to design and build enterprise applications for the cloud

Arrow left icon
Product type Paperback
Published in Dec 2010
Publisher Packt
ISBN-13 9781849680981
Length 248 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Toc

Table of Contents (23) Chapters Close

Microsoft Azure: Enterprise Application Development
Credits
About the Authors
Acknowledgement
Acknowledgement
About the Reviewer
1. Preface
1. Introduction to Cloud Computing FREE CHAPTER 2. The Nickel Tour of Azure 3. Setting Up for Development 4. Designing our Sample Application 5. Introduction to SQL Azure 6. Azure Blob Storage 7. Azure Table Storage 8. Queue Storage 9. Web Role 10. Web Services and Azure 11. Worker Roles 12. Local Application for Updates 13. Azure AppFabric 14. Azure Monitoring and Diagnostics 15. Deploying to Windows Azure Index

Accessing Table Storage


For security purposes, each request to Table Storage must be authenticated using the 256-bit shared keys created when we added the storage service. Table Storage can be directly accessed via REST, or queried using a subset of LINQ. The REST interface allows languages such as Java, PHP, and Ruby to consume Table Storage, while client libraries for ADO.NET Data Services are limited to the .NET languages.

Each request made via the REST API has a different set of required headers, and the body of each request is Atom format. Queries made via the REST API will return either 1,000 records, or run for 5 seconds (a total of 30 seconds from scheduling/processing to completion). If a query crosses these boundaries, a continuation token will be returned, which can be used in a subsequent request. Responses from the REST API are in AtomPubformat (http://en.wikipedia.org/wiki/Atom_(standard)). The ADO.NET Data Services client libraries do not have query boundaries.

An important...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime