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

command token mapping oddity #37

Open
konimaru opened this issue May 21, 2019 · 3 comments
Open

command token mapping oddity #37

konimaru opened this issue May 21, 2019 · 3 comments
Milestone

Comments

@konimaru
Copy link

Is this token mapping on purpose (if so why?) or is it really just a bug?

case SSCP_TKN_JOIN: name = "HTTP"; sep = ':'; break;

@dbetz
Copy link
Collaborator

dbetz commented May 21, 2019

Parallax asked for that mapping. I think it was a last minute change. I guess the token name should have been changed as well.

@konimaru
Copy link
Author

konimaru commented May 21, 2019

The reason I raised this issue is that there is a mapping for HTTP and this one (above) for JOIN. Both get mapped to HTTP which can't be right. A token based join command simply wouldn't work.

case SSCP_TKN_JOIN:     name = "HTTP";    sep = ':'; break;
case SSCP_TKN_CHECK:    name = "CHECK";   sep = ':'; break;
...
case SSCP_TKN_FRUN:     name = "FRUN";    sep = ':'; break;
case SSCP_TKN_HTTP:     name = "HTTP";    sep = ','; break;

@dbetz
Copy link
Collaborator

dbetz commented May 21, 2019

Hmmm... I'll have to look into that further. I remember Parallax asking for a "JOIN" command but maybe there was an error made in implementing it. Thanks for pointing this out.

@PropGit PropGit added this to the 2019 Release milestone Jul 30, 2019
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

3 participants