SSWG Meeting notes: June 3, 2026

Server Workgroup Updates
1

Action items

  • :a: Simon Pilkington: Ping the internal thread to request sign-off on the previous meeting notes that were posted but not yet reviewed.

  • :a: Simon Pilkington: Review and polish the draft of the updated working group charter and publish it for review within the next couple of days.

  • :a: Simon Pilkington: Post a link to the Swift CIDR library repository so meeting participants can review it and submit questions beforehand for discussion in the next meeting.

Agenda and action items

  • Meeting attendance noted as small; Simon added a couple of agenda items and asked for additions.
  • Simon will ping the internal thread to get sign-off on previous meeting notes because no one had reviewed them yet.
  • Simon referenced an action item where Tibor added a message about the Swift server example and asked for updates; Tibor had no new information but expressed interest in the example project.

Swift server example follow-up

  • Tibor confirmed no new updates on the Swift server example but knows contributors involved in related educational efforts (Nick and Owen).
  • Sebastien referenced previous Swift server conference work and education-team involvement aiming to expand on last year's London efforts.
  • Team expressed curiosity and will await further information on that example project.

Charter update plan

  • Simon has drafted an updated working group charter and plans to review and polish it before publishing for review in the next couple of days.
  • The charter will update scope to reflect the broader ecosystem and more working groups compared to the original.
  • The goal is to shift scope to better represent current and intended work of the group.

Forum post: new web framework

  • Sebastien flagged a new, recently created web framework repo posted by an unknown developer; initial suspicion prompted a full code review.
  • Sebastien reviewed the code and concluded the current version appears genuine and contains interesting API ideas (e.g., builder DSL and macro for routes).
  • The post was temporarily flagged as spam but has been restored; Sebastien shared the link on the chat and asked the group to monitor and provide feedback if concerns arise.

Proposal: broaden scope toward networking and infrastructure

  • Craig introduced the Swift CIDR library and proposed the working group consider expanding focus from primarily HTTP/application networking to include protocol-level and infrastructure use cases (BGP LS, RPKI, routers).
  • Craig emphasized production needs (large IP processing files) and asked if the group would support showcasing Swift for infrastructure-level performance similar to Rust examples.
  • Simon and Sebastien noted the current networking vision leans toward HTTP because of common use cases; Simon said smaller use cases like gRPC and infrastructure-specific work could fall under server-side umbrella if demonstrated as valuable.

Standardization and library compatibility discussion

  • Simon suggested the group could help identify building blocks and standardize canonical types that enable server-side Swift adoption; Craig offered the CIDR library as a candidate for feedback and possible standardization.
  • Mahdi and Tim discussed practical blockers: Mahdi noted macOS deployment constraints (support down to 10.14) and issues with using SwiftNIO/SPAN APIs, which complicated library adoption
  • Simon proposed advertising Craig's repo for review before the next meeting and having Craig present the library to the group so members can provide feedback and ask questions.

Events and logistics

  • Tim reminded attendees about an in-person Swift contributor meetup during WWDC week and encouraged applications and attendance.
  • Tim reported ongoing discussions regarding the Swift Server Side conference and expected clearer information by the next meeting.