nats.zig/examples/request_reply.zig
torque 65ab46f714
connection: eliminate String method variants
After contemplating this for a little bit, there's no point in exposing
these separately from the plain variants. Even nats.c internally calls
its plain variants after calling `strlen` on the input. Zig benefits
from having nicer pointer types than C, so we get "string" handling
for free from the fact that the standard variants take slices anyway.
2023-08-23 22:27:33 -07:00

48 lines
1.3 KiB
Zig

const std = @import("std");
const nats = @import("nats");
fn onMessage(
userdata: *bool,
connection: *nats.Connection,
subscription: *nats.Subscription,
message: *nats.Message,
) void {
_ = subscription;
std.debug.print("Subject \"{s}\" received message: \"{s}\"\n", .{
message.getSubject(),
message.getData() orelse "[null]",
});
if (message.getReply()) |reply| {
connection.publish(reply, "salutations") catch @panic("HELP");
}
userdata.* = true;
}
pub fn main() !void {
const connection = try nats.Connection.connectTo(nats.default_server_url);
defer connection.destroy();
var done = false;
const subscription = try connection.subscribe(bool, "channel", onMessage, &done);
defer subscription.destroy();
while (!done) {
const reply = try connection.request("channel", "greetings", 1000);
defer reply.destroy();
std.debug.print("Reply \"{s}\" got message: {s}\n", .{
reply.getSubject(),
reply.getData() orelse "[null]",
});
}
const stats = try connection.getStats();
std.debug.print(
"Server stats => {{\n\tmessages_in: {d} ({d} B),\n\tmessages_out: {d} ({d} B),\n\treconnects: {d}\n}}\n",
.{ stats.messages_in, stats.bytes_in, stats.messages_out, stats.bytes_out, stats.reconnects },
);
}