Hey Mike
Did you add the channel to the UserSocket on page 32? A complete code for hello_sockets distributes with the book and may help here.
sb8244
Author of Real-Time Phoenix
oldpond
Thanks for the quick response, Steve. I restarted my server, and it picked up the channel. Getting a correct response now. I shall forge ahead. Running on Manjaro linux with Firefox Developer beta. The messages tab in the dev tools view is not working so far.
2
oldpond
FYI, I moved to the unstable branch and the messages tab works in 71.0b7 of Firefox Developer.
1
sb8244
Author of Real-Time Phoenix
Thanks for sharing. I’m honestly not sure what’s up with this. I have been using Chrome exclusively, and I originally checked in Firefox that this all worked as expected. I’m glad it’s working in the latest version (although not main yet).
Chrome recently had some weird WebSocket issues as well.
1
oldpond
sb8244
Author of Real-Time Phoenix
We shipped chapter 10 to beta, and 11-13 are in editor review. 10 is about using Tracker/Presence. We build an admin UI for the store and use Presence for knowing how many of each shoes are in carts.
Chapter 13 is a LiveView chapter (it wasn’t in the original ToC as we were working out how to include it).
4
kokolegorille
Thanks for releasing part 2 of the book.
I would like to ask You if using one product channel, instead of one channel per product is also a viable option. Each message being tagged with product_id.
I do understand it solves different problems, but my concern is about the number of products, and thus, the numbers of channels You need to open (for a catalog that could 10k-100k products).
Thanks for taking time.
1
sb8244
Author of Real-Time Phoenix
Definitely! The reason I went with the multi channel approach is to hide information a bit. Also, to reduce the number of messages going out to users.
Let’s say that you have 1000 products represented by a single topic. If any of those products would change, every current visitor would receive the message. This could end up being a lot of additional data transfer in a high traffic store. It’s all a trade-off though. It’s arguably a simpler design and so development and maintenance efforts will be less. Many people would opt for this.
I don’t think either solution is wrong unless it proves itself to not work in the context of what you’re doing.
1
sb8244
Author of Real-Time Phoenix
Alright, a little update.
The deployment chapter (11) just went into beta. There’s some neat stuff to think about with load balancing here. Part III will be fairly standalone and you could read it without the rest of the book if you want.
The next 2 chapters (Managing Production Resources and Hands-On With Phoenix LiveView) are going to be releasing soon, although the holidays may delay them a bit.
We’re adding another chapter on single-page apps. I’m probably going to focus on React only here because the important part is using a component based library, and also React works with Native. I haven’t fully decided yet. The React example will probably be standalone though, and not tied into the rest of the book’s example.
- Steve
3
jimmycoyne
Anyone else having an issue opening the B5.0 ePub file with Books on iOS ? Not sure if it’s related to the formatting issues I’m seeing.
| ​ | ​# cURL command abbreviated, paste your copied command​ |
|---|---|
| ​ | ​# Include all of the headers that came with the copied command​ |
| ​ | ​$ ​​curl​​ ​​-i​​ ​​'http://localhost:4000/socket/websocket?vsn=2.0.0’​​ ​​-H…​ |
| ​ | HTTP/1.1 101 Switching Protocols |
| ​ | connection: Upgrade |
| ​ | date: Fri, 12 Apr 2019 01:29:18 GMT |
| ​ | sec-websocket-accept: afAAVeJV/iyu1ZxFEE6HMzL0ha0= |
| ​ | server: Cowboy |
| ​ | upgrade: websocket |
0