0.1.2 - EPH

• Fixed an issue reported in #80.

0.2.2 - EH

• Fixed the partitionkey issue while sending events. #73.
• Bumped the minimum dependency on rhea to 0.2.13. This gives us type definitions for rhea.
• rpc.open() returns the connection object. This makes it easy to extract common functionality to a
  separate library.

0.2.1 - EH

• Added support to create EventHubClient from an IotHub connectionstring. The following can be done

const { EventHubClient } = require('azure-event-hubs');

async function main() {
  const client = await EventHubClient.createFromIotHubConnectionString(process.env["IOTHUB_CONNECTION_STRING"]);
  const hubInfo = await client.getHubRuntimeInfo();
  console.log(hubInfo);
  await client.close();
}

main().catch((err) => {
  console.log(err);
});

• Internal design changes:
  • ManagementClient also does cbs auth before making the management request.
  • EventHubSender, EventHubReceiver, ManagementClient inherit from a base class ClientEntity.
  • Moved opening the connection to CbSClient as that is the first thing that should happen after opening the connection. This reduces calls to rpc.open() all over the sdk and puts them at one place in the init() method on the CbsClient.

0.2.0 - EH

• Added functionality to encode/decode the messages sent and received.
• Created an options object in the client.createFromConnectionString() and the EventHubClient constructor. This is a breaking change. However moving to an options object design reduces the chances of breaking changes in the future.
  This options object will:
• have the existing optional tokenProvider property
• and a new an optional property named dataTransformer. You can provide your own transformer. If not provided then we will use the DefaultDataTransformer. This should be applicable for majority of the scenarios and will ensure that messages are interoperable between different Azure services. It fixes issue #60.

0.1.1 - EPH

• Fix dependency version.

0.1.0 - EPH

• First version of azure-event-processor-host based on the new azure-event-hubs sdk.
• This client library makes it easier to manage receivers for an EventHub.
• You can checkpoint the received data to an Azure Storage Blob. The processor does checkpointing
  on your behalf at regular intervals. This makes it easy to start receiving events from the point you
  left at a later time.

0.1.1 - EH

• Changed receiveOnMessage() to receive(). This makes the naming convention consistent with other language sdks.

0.1.0 - EH

• Previously we were depending on amqp10 package for the amqp protocol. Moving forward we will be depending on rhea.
• The public facing API of this library has major breaking changes from the previous version 0.0.8. Please take a look at the Readme and the examples directory for detailed samples.
• Removed the need to say client.open.then(). First call to send or receive a message or get metadata about the hub or partition will establish the AMQP connection.
• Added support to authenticate via Service Principal credentials, MSITokenCredentials, DeviceTokenCredentials.
  • This should make it easy for customers to login once using the above mentioned credentials,
    • Create the EventHubs infrastructure on the Azure management/control plane programmatically using (azure-arm-eventhubs) package over HTTPS prtocol.
    • Use the same credentials to send and receive messages to the EventHub using this library over AMQP protocol.
• Added capability to send multiple messages by batching them together.
• Added capability to receive predefined number of messages for a specified amount of time. Note that this method will receive all the messages and return an array of EventData objects.
• Added capability to create an epoch receiver.
• Simplified the mechanism to specify the EventPosition from which to receive messages from the EventHub.
• Added proper TypeScript type definitions to the library that improves the intellisense experience for our customers.

Azure Event Hubs SDK for Node.js Preview v0.0.8

• Fixes a race condition within the AMQP redirection code when using an IoT Hub connection string
• Disable auto-retry of AMQP connections in amqp10 since the current client is not built to handle them and fails when retrying.

Azure Event Hubs SDK for Node.js Preview v0.0.7

Pulled changes for #14 and #20/#21.
Special thanks to @kurtb and @ali92hm for their contributions!