[
https://issues.apache.org/jira/browse/THRIFT-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043722#comment-17043722
]
Jens Geyer edited comment on THRIFT-5084 at 2/24/20 6:04 PM:
-------------------------------------------------------------
Would it make sense to switch to a more recent Swift version or would that be a
bridge too far? I don't use it myself, in case this is a stupid question.
was (Author: jensg):
Would it make sense to switch to a more recent version or would that be a
bridge too far?
> Swift: Server-side support for Multiplexing Services
> ----------------------------------------------------
>
> Key: THRIFT-5084
> URL: https://issues.apache.org/jira/browse/THRIFT-5084
> Project: Thrift
> Issue Type: Improvement
> Components: Swift - Library
> Affects Versions: 0.13.0
> Reporter: Alexander Edge
> Assignee: Alexander Edge
> Priority: Blocker
> Labels: multiplex
> Fix For: 0.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The Swift library features {{TMultiplexedProtocol}} but not
> {{TMultiplexedProcessor}}, which is required for use server-side.
> I've added {{TMultiplexedProcessor}}, following the same patterns as the
> other language libraries. -I've marked this issue as _Breaking-Change_ since
> it removes the {{associatedType}} from the {{TProcessor}} protocol-. I've
> removed the {{associatedType}} from {{TProcessor}} otherwise it makes it
> impossible for {{TMultiplexedProcessor}} to implement {{TProcessor}}. By
> definition it should support processors of multiple services, not a single
> service.
> I've added tests which require a change to {{Package.swift}} to run using
> {{swift test}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
