Skip to content
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

Remove Siphon Server #85

Closed
joeljfischer opened this issue Feb 17, 2015 · 5 comments
Closed

Remove Siphon Server #85

joeljfischer opened this issue Feb 17, 2015 · 5 comments
Labels
best practice Not a defect but something that should be improved anyway
Milestone

Comments

@joeljfischer
Copy link
Contributor

Major version change

The siphon server cannot currently be used by developers. It requires Ford-proprietary, closed-source, Windows-only software right now. Alternatives should be discussed.

@joeljfischer joeljfischer added the best practice Not a defect but something that should be improved anyway label Feb 17, 2015
@joeljfischer joeljfischer added this to the 4.0.0 milestone Feb 17, 2015
@jmarchwi-ford
Copy link

Perhaps we can open source the Siphon server software, add it here, and put together a roadmap/timeline for its development/purpose/etc.

@Heath-FoMoCo
Copy link

Open sourcing the siphon software it not an option. Siphon was develop with the purpose of Ford use only and making changes to be open source would not be beneficial.

@joeljfischer
Copy link
Contributor Author

Honestly, in addition to that, I do believe there are better options available. My preferred one that I would like to investigate is using an open-source HTTP server to serve a webpage from the device to the local network, which could then be viewed from any web browser that supports sockets. We're currently awaiting feedback from the lawyers regarding the use of MIT & Apache 2.0 software in our open-source projects for this and other purposes.

This would likely be implemented as another weakly linked framework, the main framework would look for it at runtime and use it if available, and no-op if it's not there. This would also allow developers to automatically use the framework in debug builds only, which is a vast improvement.

@joeljfischer joeljfischer modified the milestones: 5.0.0, 4.0.0 Mar 9, 2015
@joeljfischer
Copy link
Contributor Author

@Heath-FoMoCo is this still in use? Do you think that Relay supersedes it? It seems like Relay and this attempt to accomplish the same thing, but Relay does it better.

@asm09fsu
Copy link
Contributor

@joeljfischer so NSLog (when compiled with iOS 10) actually uses the new Unified Logging system. This means that for now, we do not have to do special modifications to handle that, however if we'd like to improve the ability to filter, we can investigate creating a custom log object

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
best practice Not a defect but something that should be improved anyway
Projects
None yet
Development

No branches or pull requests

4 participants