feat: adapt client and generator to sails header v1

[m62624]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @m62624, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request implements a significant architectural change in the sails framework by upgrading its internal message header to version 1. This update streamlines client-server communication by introducing a more efficient, binary-encoded header that uses numeric identifiers for services and their methods/events. The changes span across client code generation, existing client implementations, and core sails traits, ensuring all components are aligned with the new protocol. This refactoring aims to improve performance and provide a more robust foundation for future development.

Highlights

• New Sails Header v1 Adoption: The client and generator have been adapted to use a new sails header version (v1) for message encoding and decoding, moving away from string-based routing to a more structured binary format.
• Numeric Route and Entry IDs: Service calls and events now utilize numeric route_idx (u8) and entry_id (u16) constants for identification, replacing the previous string-based Route identifiers.
• Introduction of Identifiable Trait: A new Identifiable trait has been introduced for services and events, providing a const INTERFACE_ID: InterfaceId to uniquely identify interfaces.
• Updated io_struct_impl! Macro: The io_struct_impl! macro has been enhanced to accept entry_id and INTERFACE_ID, enabling the generation of client code that correctly incorporates the new header format.
• Simplified Encoding/Decoding Methods: Client-side methods like encode_params_with_prefix and decode_reply_with_prefix have been replaced with encode_call and decode_reply (or decode_reply_with_header), which automatically handle the new header structure.
• Refactored CallCodec and Event Traits: The CallCodec trait now uses ENTRY_ID (u16), and a new ServiceCall trait combines CallCodec with Identifiable. The Event trait has been updated to rely on Identifiable and the new header for event decoding.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a significant and well-executed refactoring to adopt the Sails header v1 protocol. The changes systematically replace the previous string-based routing with a more efficient and robust binary header mechanism utilizing interface, route, and entry IDs. The client generator, core client logic, and all associated examples and benchmarks have been consistently updated to support this new protocol. The introduction of the Identifiable and ServiceCall traits provides a clean abstraction for the new communication model. Overall, this is an excellent improvement for the framework's performance and maintainability. I have one suggestion regarding a potential performance optimization in event decoding.