-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Meta] Evaluate presentation screen discovery mechanisms #5
Comments
The evaluations should cover the following criteria (non-exhaustive):
|
@mfoltzgoogle you can count on me for the discovery part. I will first start with SSDP/DIAL. |
@louaybassbouss Please let me know if I can help with the DIAL related aspects. |
@mwatson2 sorry for late reply, yes I will let you know if I need help. I am not sure if in the evaluation of discovery protocols we need to consider DIAL or only SSDP. I think the DIAL API part (POST/GET/DELETE HTTP requests on the /apps/... endpoint) could be evaluated in the "Protocol Signalling". What do you think? |
As input to the evaluation, here's some previous work from myself and a colleague - there may be some useful info on mDNS and SSDP. |
@mfoltzgoogle @mwatson2 @chrisn I just submitted the PR #20 which contains the SSDP evaluation. feel free to review and comment. |
We've landed initial evaluations for #6 and #7. There are some follow up items around security and data collection which are tracked under separate issues linked from the main documents. @chrisn Apologies, but I missed #5 (comment) you made some time ago with the MediaScape report on discovery. I'll definitively take a look before closing this meta-issue out. |
@chrisn, I deep linked to your literature review in the README - thanks for noting it as I wasn't familiar with some of the technologies listed. |
Many thanks @mfoltzgoogle, I've just edited the review to bring a few parts up to date. |
This issue covers evaluation of presentation screen discovery mechanisms.
Per the charter scope, the focus will be on LAN discovery mechanisms. The following have been proposed thus far:
(If there are any I have missed, please reply to this issue.)
The task for each is to evaluate them along the functional and non-functional requirements, and make an initial recommendation to explore further.
The text was updated successfully, but these errors were encountered: