Preparing for Application and Service Deployment-Differences Between the Storage Emulator and Window

转载 2012年01月02日 08:04:40

http://msdn.microsoft.com/en-us/library/gg433135.aspx

The Windows Azure storage emulator acts as a local emulator for Windows Azure storage services, so that you can build and test your application before you deploy it as a hosted service to the Windows Azure. Some differences exist between using the storage emulator and using Windows Azure storage services.

General Differences

The following general differences apply to storage services:

  • The storage emulator supports only a single fixed account and a well-known authentication key. This account and key are the only credentials permitted for use with the local storage services. They are:

    Account name: devstoreaccount1
    Account key: Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==
    
    ImportantImportant
    The authentication key supported by the storage emulator is intended only for testing the functionality of your client authentication code. It does not serve any security purpose. You cannot use your production storage account and key with the storage emulator. You should not use the local storage account with production data.

  • The storage emulator is not a scalable storage service and will not support a large number of concurrent clients.

  • The URI scheme supported by the storage emulator differs from the URI scheme supported by the cloud storage services. The development URI scheme specifies the account name as part of the hierarchical path of the URI, rather than as part of the domain name. This difference is due to the fact that domain name resolution is available in the cloud but not on the local computer. For more information about URI differences in the development and production environments, see Using storage service URIs in Overview of the Windows Azure Storage Emulator.

Differences for Blob Service

The following differences apply to the Blob service:

  • The local Blob service only supports blob sizes up to 2 GB.

  • If two requests attempt to upload a block to a blob that does not yet exist in the storage emulator, one request will create the blob, and the other may return status code 409 (Conflict), with storage services error code BlobAlreadyExists. This is a known issue.

  • Put Blob operation may succeed against a blob that exists in the storage emulator and has an active lease, even if the lease ID has not been specified as part of the request. This is a known issue.

Differences for Table Service

The following differences apply to the Table service:

  • Date properties in the Table service in the storage emulator support only the range supported by SQL Server 2005 (For example, they are required to be later than January 1, 1753). All dates before January 1, 1753 are changed to this value. The precision of dates is limited to the precision of SQL Server 2005, meaning that dates are precise to 1/300th of a second.

  • The storage emulator supports partition key and row key property values of less than 900 bytes. The total size of the account name, table name, and key property names together cannot exceed 900 bytes.

  • The total size of a row in a table in the storage emulator is limited to less than 1 MB.

  • The storage emulator does not validate that the size of a batch in an entity group transaction is less than 4 MB. Batches are limited to 4 MB in Windows Azure, so you must ensure that a batch does not exceed this size before transitioning to the Windows Azure storage services.

  • In the storage emulator, querying on a property that does not exist in the table returns an error. Such a query does not return an error in the cloud.

  • In the storage emulator, properties of data type Edm.Guid or Edm.Binary support only the Equal (eq) and NotEqual (ne) comparison operators in query filter strings.

Differences for Windows Azure Drives

The following differences apply to the Windows Azure drives:

  • When mounting a Windows Azure drive from the Windows Azure compute emulator, the drive must be backed by a page blob created in the storage emulator. It is not possible to mount a drive from the compute emulator that is backed by a page blob in Windows Azure. This behavior differs from that of the other Windows Azure storage services, which can be accessed in the cloud from code that is running in the compute emulator.

  • When creating a new Windows Azure drive from the compute emulator, be sure to specify the credentials for the local storage account.

Windows Azure Storage Emulator 无法安装和无法启动问题

今天一大早起来就遇到两个坑爹问题,首先,是Windows Azure Storage Emulator无法工作,重复尝试多次后无果,最终卸载windows Azure Sdk 2.4重新安装,安装Wi...
  • baidu_21132571
  • baidu_21132571
  • 2015年08月13日 13:48
  • 601

本地存储之application cache和localstorage

第一部分:Application Cache 1.Application Cache介绍   html5提供的一种应用缓存机制,使得基于web的应用程序可以离线运行。优点有如下几点:   离线浏览:...
  • kingliguo
  • kingliguo
  • 2016年09月23日 12:52
  • 1338

Android 新建模拟器不能运行emulator: emulator window was out of view and was recentered

Android N预览版镜像出来了,用Android studio更新了sdk后发现模拟器不能跑,出错日志大致如下: Created filesystem with 11/4224 inodes a...
  • u013318150
  • u013318150
  • 2016年03月11日 14:28
  • 1307

There is a circular dependency between XMPPFramework/Core and XMPPFramework/Authentication

执行"pod install" 或者 "pod update" , xmppframework 会出现循环依赖问题。 There is a circular dependency betwe...
  • CB1234CB
  • CB1234CB
  • 2015年06月29日 09:41
  • 891

正确创建AVD,告别功能不全的Genymotion

emulator: WARNING: Crash service did not start 模拟器:警告:崩溃服务没有启动 ...
  • u012585964
  • u012585964
  • 2016年07月09日 13:03
  • 6619

Preparing for Application and Service Deployment-Azure Lessons from the Trenches

http://www.kindohm.com/post/235271466/azurelessons.html For the past two months I’ve had the fort...
  • riverlau
  • riverlau
  • 2012年01月02日 08:09
  • 305

emulator window was out of view

1、如果skin的显示区域太大,键盘部分可能显示不全,给使用带来不便模拟器还会报出警告: emulator window was out of view and was recentred我们可以通过...
  • youth0532
  • youth0532
  • 2011年07月14日 14:42
  • 2507

Shared storage cannot protect your application from code injection attacks

在动态加载dex的时候可能会出现以下问题:  java.lang.IllegalArgumentException: Optimized data directory /storage/emulat...
  • parallelyk
  • parallelyk
  • 2016年06月29日 15:32
  • 654

Preparing for the Sample Application

Preparing for the Sample ApplicationThe sample application is built using Microsoft SQL Servers Nort...
  • masterall
  • masterall
  • 2005年09月02日 22:43
  • 730

Android开发之关于“Unable to add window - token null is not for an application ”的异常

关于Unable to add window -- token null is not for an application 的错误 最近在写到ProgressDialog的时候 报错: andr...
  • yangkeshihaer
  • yangkeshihaer
  • 2014年10月16日 10:52
  • 1492
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:Preparing for Application and Service Deployment-Differences Between the Storage Emulator and Window
举报原因:
原因补充:

(最多只允许输入30个字)