ChrisPenner / ChrisPenner/rasa
Remote UI protocol
- Dominant language
- Haskell
- Stars
- 625
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
In regards to remote UI protocal #8 @ChrisPenner, I have a proposal of the following. Currently it is just the update part of the communication, there should also be another part about how to handling event.
I am not quite good at Haskell and, and it seems that if we standardized the protocol, it does not have to be for remote UI. I am not quite good at Haskell and I appreciate any suggestions.
I put my proposal into a [gist](https://gist.github.com/DarwinSenior/4638e21df3f1be79fbe65c7d0a45fda0). Any comments are welcome.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the referenced remote UI protocol issue (#8) and the proposal in the linked gist. The issue only describes an update protocol and mentions a future event-handling part, so first clarify the intended scope and acceptance criteria. Done would require an agreed protocol proposal, but no implementation files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100