Obsolete Tauri v1 IPC mechanism?

[safizn]

Hi, asking for custom invoke system plugin development.

1. Is Tauri v1 communication mechanism obsolete and the path forward would be entirely relying on the Tauri v2 communication mechanism?

• Investigating source code reveals that Commands, Events, Channels all use v2 URI fetch mechanism.

• Tauri v1 message passing mechanism seem to be used only for compatibility cases, like on Android which doesn't support custom URI protocl.

2. Are there any features that still solely function using Tauri v2 direct ipc communication mechanism?

---

Tauri v2 message passing mechanism:

• relies on custom protocol URI schemes.
• triggered from JS with fetch() Web API
• registers handler in tauri::manager::webview::prepare_pending_webview()

      if !registered_scheme_protocols.contains(&"ipc".into()) {
        let protocol = crate::ipc::protocol::get(manager.manager_owned());
        pending.register_uri_scheme_protocol("ipc", move |webview_id, request, responder| {
          protocol(webview_id, request, UriSchemeResponder(responder))
        });
        registered_scheme_protocols.push("ipc".into());
      }
  

Tauri v1 message passing mechanism:

• relies on IPC through direct webview API
• triggered in JS with window.ipc.postMessage()
• registers ipc handler in tauri-runtime-wry::create_webview()

    webview_builder = webview_builder.with_ipc_handler(create_ipc_handler(
      kind,
      window_id.clone(),
      id,
      context.clone(),
      label.clone(),
      ipc_handler,
    ));
  
  

[ahkohd]

I just refactored this to tauri v2: https://github.com/ahkohd/tauri-awesome-rpc

Slightly ready, adding some finishing touches

[safizn]

Awesome! I've studied this plugin before together with other implementations to grasp the constraints & issues that may arise. Thanks I will take a look at the changes.

• https://github.com/ahkohd/tauri-awesome-rpc
• https://github.com/tauri-apps/tauri-invoke-http
• https://github.com/JonasKruckenberg/tauri-plugin-graphql

[safizn]

Tauri v1 window.ipc.postMessage() message passing mechanism is only used for compatibility and as a fallback mechanism when fetch fails.

tauri/crates/tauri/scripts/ipc-protocol.js

Line 68 in fd63f22

} else {