search

eclipse-uprotocol / up-spec

uProtocol Specifications
Apache License 2.0
33 stars 25 forks source link

Make definition of RpcClient more formal #150

Closed sophokles73 closed 5 months ago

sophokles73 commented 5 months ago

Use UML2 to define interfaces, added sequence diagrams illustrating behavior.

Might serve as inspiration for addressing #129

stevenhartley commented 5 months ago

@sophokles73 (et. al.), I tried a different approach for defining these L2 APIs here: https://github.com/eclipse-uprotocol/up-spec/pull/151 Let me know your thoughts. I'm going with a much more open specifications at this layer giving a lot more freedom for the language libraries to specify what they feel is needed in lieu of trying to make everything look the same across all programming languages.

PLeVasseur commented 5 months ago

I'm going with a much more open specifications at this layer giving a lot more freedom for the language libraries to specify what they feel is needed in lieu of trying to make everything look the same across all programming languages.

Hmm :thinking: Is it feasible to write down much in the spec for uP-L2 then? Are there certain things in your mind which are more-or-less indisputable vs things which a language implementation is free to do?

Edit: Ah, perhaps I should go read #151

Edit the 2nd: Oh, so your thoughts are that not much is sacred and leave most of the specifics to the language library.

sophokles73 commented 5 months ago

closing in favor of #151