But some of the clients they will tell you, "sorry Michael your price is way too high is totally out of the market level. I'm sorry I can't help you this time. I'm going to place the order or I have already placed the order." so if this is the attitude that means your clients is not bluffing . your really offer the wrong price. Then what you gonna do ?
>> Your price is way too high

The logic will be step No.1: I'm going to test my client's attitude because something your client is bluffing right? so I'm going to ask him : oh I'm sorry to hear that but please let me know what is your target price , how can I improve my price, and how much gap in there, so I will go back to my manufacturer and try to get more discount. maybe half half 50% of the clients they will tell you okay my target is like that or somebody is offering this much lower and you have to improve this much. so that's simply giving you a chance so in this case they were really bluffing with you.
>> Your price is way too high

If my client tell me Michael your price is way too high, you know what I'm going to say? what's is your reaction? I'm not going to tell my client "no no no, my price is very low , my price is competitive." because in this way you are simply arguing, you're arguing with your client, you disagree with your client in front of his face, and this is not polite. I'm not going to say that.
>> Your price is way too high

Solid Cable replaces the need for Redis to act as the pubsub server to relay WebSocket messages from the application to clients connected to different processes. It uses fast polling, but it’s still almost as quick as Redis, when run through the same server on SQLite.
>> Rails8

7. Reacting to negotiation activity (SDP descriptions and ICE candidate exchanges), the newcomer starts streaming to other clients.
>> webRTC Hotwire and Ruby on Rails

6. WebRTC negotiations are created by each of the other clients, and they start streaming to the newcomer.
>> webRTC Hotwire and Ruby on Rails

5. TurboStream updtes create video elements on each of the other clients' screens.
>> webRTC Hotwire and Ruby on Rails

4.The newcomer creates a WebRTC negotiation and sends a greeting back to each of the other clients.
>> webRTC Hotwire and Ruby on Rails

2. The connected clients greet this newcomer letting them know their ID.
>> webRTC Hotwire and Ruby on Rails

Finally, when a client disconnects from the room channel, a Turbo Stream update removes the media element from the screen. The media controller broadcasts its removal so the room controller can clean up.
>> webRTC Hotwire and Ruby on Rails

This kicks off the complex exchange of SDP descriptions and ICE candidates, and once either is received by the newcomer, it can start the streaming process from its own stream to the other client. Now all clients are streaming to and from each other.
>> webRTC Hotwire and Ruby on Rails

This time though, instead of a greeting (which would be very polite,but awkward and endless!), the client starts streaming to the other client, by adding media tracks to the connection.
>> webRTC Hotwire and Ruby on Rails

This triggers the same process as above on the other client: appending a media element via a Turbo Stream update, and starting a webRTC negotiation.
>> webRTC Hotwire and Ruby on Rails

Once the negotiation has been created, the newcomer client notifies the other client by reciprocating the greeting i.e. calling greet on the room channel.
>> webRTC Hotwire and Ruby on Rails

Anyway, the code for this has been mostly lifted from the spec and handled by the Signaller /WebrtcNegotiation. When creating the negotiation, the room controller listens for track events on the TRCPeerConnection, so it can start streaming from the remote client.
>> webRTC Hotwire and Ruby on Rails

The negotiation is "perfect" as it ensures that the RTCPeerConnection is in the correct state for setting descriptions, and avoids collision errors by having one client be "polite" and other "impolite"-the polite one backs down in the case of a collision.
>> webRTC Hotwire and Ruby on Rails

It's important we do this first so that it's ready for incoming streams. The medium controller messages the room controller to notify that it has been added. This begins the WebRTC negotiation to form a connection between the two clients.
>> webRTC Hotwire and Ruby on Rails

The greet action broadcasts specifically to the newcomer, a Turbo Stream update which appends a media element representing the remote client.
>> webRTC Hotwire and Ruby on Rails

Once connected, the room channel broadcasts the presence of this new client.Each connected client then "greets" this newcomer by calling the greet action on the room channel and specifying to and from fields.
>> webRTC Hotwire and Ruby on Rails

The Stimulus room controller handles Enter button click.It gets the user's local audio and video and feeds them into the local video element. It also starts Action Cable subscriptions specific to the current room: one for communicating WebRTC messages: the Signaller; and one for clients to ping others: the RoomSubscription.
>> webRTC Hotwire and Ruby on Rails

We are going to wait, and we are going to wait we are going to wait, until they feel the pain, until they start to bleed that is what I want yeah, but what about our clients, they've been trusting us with their savings.
>> The Big Short大空头（2015） Movie Script

So let me get this straight the bank calls you up they give you the bonds they wanna sell they give you clients, they give you money to run your business, give you fat fee's for doing so but you represent the investors?
>> The Big Short大空头（2015） Movie Script

Because we need to be able to expense the ammo to a client!
>> The Big Short大空头（2015） Movie Script