Skip to content
This repository has been archived by the owner on Aug 17, 2020. It is now read-only.

Transition from most Sockets to request/response by expressjs #20

Closed
Shadow53 opened this issue Apr 25, 2016 · 1 comment
Closed

Transition from most Sockets to request/response by expressjs #20

Shadow53 opened this issue Apr 25, 2016 · 1 comment
Labels
bug enhancement important

Comments

@Shadow53
Copy link
Owner

After looking more at expressjs request/response, I don't know why I was implementing so much in sockets that would be better as GET/POST requests. Therefore, basically everything but adding/removing help requests - so logging in and anything on an admin page - should be done with request/response, whether through forms or $.ajax().
@Shadow53 Shadow53 mentioned this issue Apr 25, 2016
Closed
@Shadow53
Copy link
Owner Author

Fixed this at the same time as issue #11 in version 0.6.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug enhancement important
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Shadow53