𝗕𝗲𝘆𝗼𝗻𝗱 𝗛𝗧𝗧𝗣 𝗶𝗻 𝗥𝘂𝘀𝘁: 𝗥𝗲𝗮𝗹-𝗧𝗶𝗺𝗲 𝗦𝗼𝗰𝗸𝗲𝘁𝘀 𝗮𝗻𝗱 𝗙𝗧𝗣
HTTP is great for most tasks. But it falls short in two specific areas.
Real-time push. Browsers need to know when something happens immediately. Raw WebSockets work, but you must write all the logic for reconnection and routing yourself. Socket.IO is the standard for JavaScript developers, but Rust lacked a good server implementation until recently.
File transfer via FTP. Legacy systems and media pipelines use FTP everywhere. The Rust async ecosystem had a gap here for a long time.
This post shows you how to bridge these gaps. We build a Socket.IO server and an FTP server. Then we connect them. When a file uploads via FTP, the system instantly notifies every connected browser.
The Tools We Use:
• Socketioxide: The Rust implementation of Socket.IO. It works with any Socket.IO client like Node.js or Python. • Libunftp: A tool to build composable FTP servers. • Suppaftp: An async FTP client for Rust.
Key Features:
- Socket.IO Rooms: You can group connections. When a file uploads to a specific folder, you only notify users in that room.
- Restricted FTP: We built a custom wrapper to block destructive actions. Users can upload and download files, but they cannot delete or rename them.
- Async Integration: We use a broadcast channel to connect the FTP server to the Socket.IO server.
The Workflow:
- FTP Client uploads a file to the FTP Server.
- The FTP Server triggers a broadcast event.
- The Socket.IO server receives the event.
- The Socket.IO server emits a "file_uploaded" event to the browser.
This pattern works for more than just files. You can use it for job completion alerts, live data updates, or deployment dashboards.
The full code is available on GitHub.