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.

Sign up for GitHub

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

Jump to bottom

Connection/Client/Server core API #762

Open
Stinkfist0 opened this issue Apr 25, 2014 · 2 comments
Open

Connection/Client/Server core API #762

Stinkfist0 opened this issue Apr 25, 2014 · 2 comments
Labels
Feature Request Refactoring/Redesign Usability

Comments

@Stinkfist0
Copy link
Contributor

Tundra being inherently networked platform (though ideally this could be maybe disabled if wanted), it would be convenient to have the mostly used networking related interfaces directly in the core: Client, Server, and UserConnection.
@jonnenauha
Copy link
Member

Not just the interfaces but if I could get the pointers too with framework_->Server()->.... Going to TundraProtocolModule etc. is a pain in the ass right now.

@Stinkfist0
Copy link
Contributor Author

Yeah, by interfaces I mean exactly Fw()->Client() and Fw()->Server().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Request Refactoring/Redesign Usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonnenauha @Stinkfist0