A data access layer (DAL) class library project that handles create, read, update, and delete (CRUD) operations on the Azure Queue.
The e-mail queue
By default a queue for processing e-mails is created by the AzureProviders solution. Whenever an e-mail is to e sent it is first placed in the e-mail queue to be processed asynchronously by the
role. This is very useful as the process sending the e-mail does not have to wait until the e-mail is sent before continuing its further processing
class is the context for the AzureQueueDataSource
class. It holds information like
- the name of the e-mail queue,
- the cloud storage account in use,
- the current cloud queue client.
class also sets the number of retries before failing; by default an e-mail is attempted sent three times before being ignored. Application setting key
decides how many seconds the queue waits before retrying after a failed attempt.
requests smaller than 1460 bytes are inefficient with nagling turned on. The AzureProviders solution has turned nagling off by default, this setting is set in the
application setting key.
for information about gained advantages by turning off nagling.
class is the data source against the Azure Queue.
also handles internal operations like serializing and de-serializing to and from JSON. The e-mails that are put in the e-mail queue is stored there as
objects serialized as JSON.
Creating the e-mail queue
contains code that creates the e-mail queue, this is currently called from
. In early versions of AzureProviders this was done automatically, this was removed later since the overhead and expense was considered too much.
class is used for serializing and de-serializing e-mails as the e-mails are placed and retrieved from the e-mail queue.