Skip to content

Conversation

@oodigie
Copy link
Contributor

@oodigie oodigie commented Mar 18, 2025

The goal of this PR is to add sample(s) to demonstrate the use of the Solace PubSub+ Go API with the PubSub+ cache.

Changes:

  • EBP-30: Added howtos to demonstrate how to use the Go PubSub+ API with the PubSub+ cache.
  • Bumped version of the solace/dev/go/messaging package to v1.9.0 which is the expected release version with the PubSub+ cache support.

@oodigie oodigie marked this pull request as draft March 18, 2025 12:54
@Mrc0113 Mrc0113 requested a review from Copilot July 23, 2025 16:40
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds comprehensive how-to examples demonstrating the usage of the Solace PubSub+ Go API with the PubSub+ cache feature. The examples showcase different cache request strategies and response handling patterns to help developers understand cache integration.

  • Added a complete how-to guide with examples for all four cache request strategies (AsAvailable, CachedFirst, CachedOnly, LiveCancelsCached)
  • Demonstrated both callback-based and channel-based approaches for handling cache responses
  • Updated the Go messaging dependency to v1.9.0 to support PubSub+ cache functionality

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 9 comments.

File Description
howtos/how_to_use_pubsub_cache.go New comprehensive example file demonstrating PubSub+ cache usage with multiple strategies and response handling patterns
go.mod Updated solace messaging dependency from v1.8.0 to v1.9.0 for cache support

@oodigie oodigie marked this pull request as ready for review July 23, 2025 17:39
@Mrc0113 Mrc0113 requested a review from TamimiGitHub July 23, 2025 17:48
@TamimiGitHub
Copy link
Contributor

@oodigie can we udpate the the API version to v1.10.0 since this is the latest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants