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

Protocol for Networking Layer [Enhancement] #29

Open
paulrd opened this issue Dec 13, 2014 · 1 comment
Open

Protocol for Networking Layer [Enhancement] #29

paulrd opened this issue Dec 13, 2014 · 1 comment

Comments

@paulrd
Copy link
Contributor

paulrd commented Dec 13, 2014

I'd like to use slacker with I2P networking. This is a higher-latency socket-like (in fact it has Sockets) networking layer. It's synchronous / blocking however - unlike link / netty. I wonder if you can use a protocol for the link (https://github.com/sunng87/link) dependency. Then we could swap out link for I2P if we wanted to. This would likely take some work to wrap I2P to provide the same interface as link. I'm not sure... I just thought I would suggest this to see if it was a good idea. I'm currently making an I2P app, and it would be nice to use slacker for rpc instead of making my own.

@paulrd paulrd changed the title Protocol for Networking Layer Protocol for Networking Layer [Enhancement] Dec 13, 2014
@sunng87
Copy link
Owner

sunng87 commented Dec 14, 2014

@paulrd Actually most part of link is protocol based except the (start-tcp-server), so maybe I can spend some time to refactor it into fully protocol based. I think it might be easier to hide I2P network code behind link than behind slacker.

I will investigate I2P networking in next few days if I have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants