Closed JHYen1978 closed 5 years ago
Hey @JHYen1978,
Thanks! I can't take any credit for writing it, but I'm glad you've enjoyed it.
There's no real reason we curl
instead of visiting the site in another browser, it's only because it was a little quicker and easier to explain. Are you having issues trying to get things working when visiting localhost:3000/users
in another browser?
Hi @brianjhanson ,
I am so glad to receive the reply from you.
Now I have no problem linking to http://localhost:3000/users
either using curl
or visiting the site in another browser. I was very confused about how this example work, but now I think I get it. Correct me if my understanding is incorrect: if we turn on two browsers say, A and B, A goes to http://localhost:3000/users
and B goes to http://localhost:3000
respectively, it will act like A is a message sender and B is a receiver, right?
Based on this example, I should be able to build a web-based instant messaging platform on which A and B can do real-time chatting. If you know something like this (be sure using express-generator + socket.io) has been on shelf in github or elsewhere, please be so kind to give me the link to it.
Thank you very much!
Hi Brian, My wife became ill two years ago and died. I’m afraid I lost interest in this thread. Sorry for any inconvenience. All the best Dave PS I could not remember my GitHub password…
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Brian Hanson notifications@github.com Sent: Tuesday, October 29, 2019 2:07:38 PM To: onedesign/express-socketio-tutorial express-socketio-tutorial@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [onedesign/express-socketio-tutorial] Why does the client side have to turn on the terminal and type: curl http://localhost:3000/users? (#13)
Thanks! I can't take any credit for writing it, but I'm glad you've enjoyed it.
There's no real reason we curl instead of visiting the site in another browser, it's only because it was a little quicker and easier to explain. Are you having issues trying to get things working when visiting localhost:3000/users in another browser?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fonedesign%2Fexpress-socketio-tutorial%2Fissues%2F13%3Femail_source%3Dnotifications%26email_token%3DAFN4IZXJBAJ76KPRVTQQB3DQRA7SVA5CNFSM4JCY2JM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECQTW2Y%23issuecomment-547437419&data=02%7C01%7C%7C1f08cbd190f84f6ef94d08d75c795b75%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637079548597907600&sdata=PR5aIwR7v7rYRgvY%2FC0yeFkJogLD3iNEq7kcWvGs1v0%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFN4IZRDONQHPWGQ3LEPYDLQRA7SVANCNFSM4JCY2JMQ&data=02%7C01%7C%7C1f08cbd190f84f6ef94d08d75c795b75%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637079548597927616&sdata=6ttuX1NEVBpPyO42ZzREW%2F6LB8mB1CLBbU%2BBmc40qp8%3D&reserved=0.
Very sorry to hear that @OldGitDave. I've closed the issue for now, but feel free to open it back up if needed in the future.
Hi brianjhanson,
First of all I really like the project and the introduction you provided is very clear and comprehensive.
However, I am not sure about the final part of the introduction. That is, why do we first open up homepage at http://localhost:3000, and then pop open terminal and type: curl http://localhost:3000/users? Why does it not just done in Chrome (or other browser)?
If we would like to use express-socket.io to build a instant messaging system working on browsers, how do we do if users do not want to turn on the terminal in addition to browsers?
Thank you very much and look forward to your further instruction.
JHYen