nats.zig/examples/pub_bytes.zig

// This file is licensed under the CC0 1.0 license.
// See: https://creativecommons.org/publicdomain/zero/1.0/legalcode

const std = @import("std");
const nats = @import("nats");

pub fn main() !void {
    const connection = try nats.Connection.connectTo(nats.default_server_url);
    defer connection.destroy();

    const data = [_]u8{ 104, 101, 108, 108, 111, 33 };
    try connection.publish("subject", &data);
}
all: add missing copyright headers Tests are CC0/public domain because there's no reason for them not to be. Examples are also CC0/public domain, but this may be a little bit weird because they are largely straightforward ports of examples from nats.c which carry the Apache license. However, I personally wrote them against the zig bindings and I doubt anyone will end up in a court of law due to their software containing uselessly trivial example code. 2023-09-02 15:04:46 -07:00			`// This file is licensed under the CC0 1.0 license.`
			`// See: https://creativecommons.org/publicdomain/zero/1.0/legalcode`

examples: add pub_bytes This was the point that I realized there's no reason to have the string variants of the publishing methods. But also there's not really much point in porting the other getting-started examples, since we've covered all their functionality in the existing examples (actually, this one is redundant too, but I have already done it, so it's getting grandfathered in). Porting some of the more interesting examples might be a good idea, but those have a weird argument parser that I don't really want to port (even though it is very simple in the way that it works). For the most part, I think writing unit tests will do a better of flexing the bindings. 2023-08-23 22:35:15 -07:00			`const std = @import("std");`
			`const nats = @import("nats");`

			`pub fn main() !void {`
			`const connection = try nats.Connection.connectTo(nats.default_server_url);`
			`defer connection.destroy();`

			`const data = [_]u8{ 104, 101, 108, 108, 111, 33 };`
			`try connection.publish("subject", &data);`
			`}`