Skip to content

Support HTTP Protocol Moniker via Abstraction (On Conventions TexualConvention, BinaryConvention, ProtocolConvention) #3

Description

@juliusfriedman

Let my convention be HTTP
Let my other convention be SIP or RTSP
Let my other convention be GAME/DEVICE (HTTP COMPATIBLE)
Let my final convention be TELNET Compatible

I should be able to use the Connection I created to speak to any of the conventions underlying.

I think Bedrock might have a bit easier path there to work from but none the less I like the way your going with this but not the APIz.

E.g. I wanna be able to use some of the HTTP Convention within my SIP or GAME and then TELNET

Let me know if you need more information but en general at the 1.x level all protocols are basically a get_line and grammar checks.

https://github.com/juliusfriedman/net7mma_core/blob/e7b228cfd6ce36401e11d1d1f31b29a4e9d41ba0/Http/HttpMessage.cs
https://github.com/juliusfriedman/net7mma_core/blob/e7b228cfd6ce36401e11d1d1f31b29a4e9d41ba0/Sip/SipMessage.cs
https://github.com/juliusfriedman/net7mma_core/blob/e7b228cfd6ce36401e11d1d1f31b29a4e9d41ba0/Rtsp/RtspMessage.cs

Fun fact, some hardware uses HTTP in RTSP for various reasii, same with SIP and sometimes HTTP. Sometimes this is a bug and is fixed in later firmware (GStreamer) otherwise its just worked around via libav.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions