<commit_before>ServiceBroker.Net
========

*An NServiceBus ITransport implementation for SQL Server Service Broker*

About
-----

SQL Server Service Broker is a centralized message queuing subsystem that is provided by SQL Server. It uses logical **services** which accept messages and store them in a **queue**. Applications for that logical service can receive messages from the queue. Services are tied to **message contracts** which define which **message types** the service is able to send and/or receive.

NServiceBus is distrubted message bus application framework. It uses a distributed bus architecture in that when an application sends a message on the bus it is the responsibility of the bus to determine the correct endpoint(s) to deliever the message to. NServiceBus relies on the underlying ITransport to physically deliver the message. It lends itself well to queue based messaging subsystems, such as MSMQ or Service Broker.

Usage
-----

Using the Service Broker ITransport requires both setup of your Service Broker schema and configuration for NServiceBus.

Currently the transport uses a specific message type and message contract when sending messages via Service Broker:

    CREATE MESSAGE TYPE NServiceBusTransportMessage
        VALIDATION = NONE ;
    GO

    CREATE CONTRACT NServiceBusTransportMessageContract
        ( NServiceBusTransportMessage SENT BY ANY);<commit_msg>updating readme to point to new project<commit_after>#Update:

This project is mostly abandonded. But updated library code will be integrated into: https://github.com/jdaigle/LightRail


ServiceBroker.Net
========

*An NServiceBus ITransport implementation for SQL Server Service Broker*

About
-----

SQL Server Service Broker is a centralized message queuing subsystem that is provided by SQL Server. It uses logical **services** which accept messages and store them in a **queue**. Applications for that logical service can receive messages from the queue. Services are tied to **message contracts** which define which **message types** the service is able to send and/or receive.

NServiceBus is distrubted message bus application framework. It uses a distributed bus architecture in that when an application sends a message on the bus it is the responsibility of the bus to determine the correct endpoint(s) to deliever the message to. NServiceBus relies on the underlying ITransport to physically deliver the message. It lends itself well to queue based messaging subsystems, such as MSMQ or Service Broker.

Usage
-----

Using the Service Broker ITransport requires both setup of your Service Broker schema and configuration for NServiceBus.

Currently the transport uses a specific message type and message contract when sending messages via Service Broker:

    CREATE MESSAGE TYPE NServiceBusTransportMessage
        VALIDATION = NONE ;
    GO

    CREATE CONTRACT NServiceBusTransportMessageContract
        ( NServiceBusTransportMessage SENT BY ANY);
{'fraction_non_alphanumeric': 0.043184885290148446, 'fraction_numerical': 0.0, 'mean_word_length': 4.604914933837429, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2572122', 'n_tokens_mistral': 679, 'n_tokens_neox': 646, 'n_words': 392}