Update token source examples for create factories

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: alan-george-lk

token_source/token_source_caching.cpp

@@ -48,10 +48,10 @@ bool cachingTokenSourceConnect() {
 
   std::cout << "Caching token source wrapping endpoint: " << endpoint_url << "\n";
 
-  // Build the inner source, then wrap it. CachingTokenSource::wrap takes
+  // Build the inner source, then wrap it. CachingTokenSource::create takes
   // ownership of the inner source via unique_ptr.
-  auto inner = livekit::EndpointTokenSource::fromUrl(endpoint_url, endpointOptionsFromEnv());
-  auto token_source = livekit::CachingTokenSource::wrap(std::move(inner));
+  auto inner = livekit::EndpointTokenSource::create(endpoint_url, endpointOptionsFromEnv());
+  auto token_source = livekit::CachingTokenSource::create(std::move(inner));
 
   livekit::TokenRequestOptions request_options;
   request_options.participant_identity = "robot-a";

token_source/token_source_custom.cpp

@@ -55,7 +55,7 @@ bool customTokenSourceConnect() {
   // The callback is invoked for each fetch with the request options. Here we
   // pretend to call an internal service; in a real app this is where you would
   // talk to your own auth backend.
-  auto token_source = livekit::CustomTokenSource::fromCallback(
+  auto token_source = livekit::CustomTokenSource::create(
       [](const livekit::TokenRequestOptions& options) -> std::future<TokenResult> {
         (void)options; // A real backend would honor these (room, identity, ...).
 

token_source/token_source_endpoint.cpp

@@ -50,7 +50,7 @@ bool endpointTokenSourceConnect() {
   std::cout << "Endpoint token source: " << endpoint_options.method << " " << endpoint_url << " ("
             << endpoint_options.headers.size() << " custom header(s))\n";
 
-  auto token_source = livekit::EndpointTokenSource::fromUrl(endpoint_url, std::move(endpoint_options));
+  auto token_source = livekit::EndpointTokenSource::create(endpoint_url, std::move(endpoint_options));
 
   // These options are sent to your endpoint, which embeds them into the JWT.
   livekit::TokenRequestOptions request_options;

token_source/token_source_literal.cpp

@@ -45,7 +45,7 @@ bool literalTokenSourceConnect() {
 
   // Each fetch() returns these exact credentials; nothing is requested over the
   // network. Room and participant identity are encoded in the token.
-  auto token_source = livekit::LiteralTokenSource::fromValue(url, token);
+  auto token_source = livekit::LiteralTokenSource::create(url, token);
 
   livekit::Room room;
   ParticipantLogDelegate delegate;

token_source/token_source_sandbox.cpp

@@ -45,7 +45,7 @@ bool sandboxTokenSourceConnect() {
 
   // POSTs to cloud-api.livekit.io/api/v2/sandbox/connection-details with
   // X-Sandbox-ID set from LIVEKIT_SANDBOX_ID.
-  auto token_source = livekit::SandboxTokenSource::fromSandboxId(sandbox_id);
+  auto token_source = livekit::SandboxTokenSource::create(sandbox_id);
 
   livekit::TokenRequestOptions request_options;
   request_options.participant_identity = "robot-a";