Rust

Azure Service Bus - Send Message to Topic

See more Azure Service Bus Examples

Example code showing how to send a message to an Azure Service Bus Topic. Rust

// Note: Requires Chilkat v9.5.0.65 or greater.

// This requires the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.

// Make the initial connection.
// A single REST object, once connected, can be used for many Azure Service Bus REST API calls.
// The auto-reconnect indicates that if the already-established HTTPS connection is closed,
// then it will be automatically re-established as needed.
let rest = chilkat::Rest::new();
let b_auto_reconnect = true;
if rest.connect("<yournamespace>.servicebus.windows.net", 443, true, b_auto_reconnect).is_err() {
    println!("{}", rest.last_error_text());
    return;
}

// ----------------------------------------------------------------------------------------------
// The code above this comment could be placed inside a function/subroutine within the application
// because the connection does not need to be made for every request.  Once the connection is made
// the app may send many requests..
// ----------------------------------------------------------------------------------------------

// Let's load a previously computed SAS token and use it.
// See Azure Shared Access Signature for an example to genenerate an Azure SAS token.
let sb_token = chilkat::StringBuilder::new();
let _ = sb_token.load_file("qa_data/tokens/serviceBusSas.txt", "utf-8");

// Tell the REST object to use the Azure Shared Access Signature for authorization.
let _ = sb_token.prepend("SharedAccessSignature ");
let _ = rest.add_header("Authorization", &sb_token.get_as_string().unwrap_or_default());

// ----------------------------------------------------------------------------------------------

// The code for sending to a topic is identical to the code sending to a queue.
// The only difference is that a topic name (or topic path) is used instead of queue name/path.

// Send to a topic named "gilaMonster";
let topic_name = "gilaMonster".to_string();

// The HTTP request body contains the content of the message sent to the topic.
let sb_request_body = chilkat::StringBuilder::new();
let _ = sb_request_body.append("Hello, I'm a gila monster!");

// Build the path..
let sb_path = chilkat::StringBuilder::new();
let _ = sb_path.append("/");
let _ = sb_path.append(&topic_name);
let _ = sb_path.append("/messages");

// Add timeout and api-version query parameters.
let _ = rest.add_query_param("timeout", "20");
let _ = rest.add_query_param("api-version", "2013-08");

// Standard brokered message properties are placed in a BrokerProperties HTTP header. 
// The broker properties must be serialized in JSON format. To specify a TimeToLive value of 3600 seconds 
// and to add a message label "M1" to the message..
let json = chilkat::JsonObject::new();
let _ = json.append_int("TimeToLive", 3600);
let _ = json.append_string("Label", "A123");
let _ = rest.add_header("BrokerProperties", &json.emit().unwrap_or_default());

// To add custom properties, such as "Priority" and "Color"
let _ = rest.add_header("Priority", "High");
let _ = rest.add_header("Color", "pink");

let sb_response_body = chilkat::StringBuilder::new();
if rest.full_request_sb("POST", &sb_path.get_as_string().unwrap_or_default(), &sb_request_body, &sb_response_body).is_err() {
    println!("{}", rest.last_error_text());
    return;
}

println!("Response Status Code = {}", rest.response_status_code());

// Check for a success response.
if rest.response_status_code() != 201 {
    println!("{}", rest.last_request_start_line());
    println!("{}", rest.last_request_header());
    println!("{}", sb_response_body.get_as_string().unwrap_or_default());
    println!("Failed.");
    return;
}

// If successful, the 201 response will have no response body.

println!("Success.");