# Suggestion to design specific network client **URL:** \ **Category:** Ruby\ **Created:** [May 28, 2010, 11:18pm UTC](https://www.ruby-forum.com/t/suggestion-to-design-specific-network-client/189337 "2010-05-28T23:18:13Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![pollopoop92](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a6a055/32.png) [@pollopoop92](https://www.ruby-forum.com/u/pollopoop92)\ **Post date:** [May 28, 2010, 11:18pm UTC](https://www.ruby-forum.com/t/suggestion-to-design-specific-network-client/189337/1 "2010-05-28T23:18:13Z")
Hi, as in the object i need to realize a simple IPv6 multicast client. And I already do it with some troubles but solved. Now, i’ve to make something that every N seconds, i.e. 10s , store the data sampled until that moment and start doing other operations, but i dont have to stop the sampling action. The sampling operation have to be like a while true. I dont have any clue to accomplish that. I was thinkin to use eventmachine but i dont know if i can apply my custom setsockopts and i did not find any documentation about it. Thanks in advance, Francesco V. ---
**Author:** ![pollopoop92](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a6a055/32.png) [@pollopoop92](https://www.ruby-forum.com/u/pollopoop92)\ **Post date:** [May 29, 2010, 12:06am UTC](https://www.ruby-forum.com/t/suggestion-to-design-specific-network-client/189337/2 "2010-05-29T00:06:13Z")
On 5/28/10, Francesco V. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > did not find any documentation about it. > Um, maybe use threads? EventMachine ought to work too, but I can’t > speak to that. What is this sampling that you’re doing? What kind of samples are they and more importantly, where do they come from? You’re gonna need some kind of (hardware or software) buffering in order to ensure that no samples get lost. The size of that buffer lets you know how long your program can ‘go away’ and do other things (like network i/o) before you start losing data. HTH ---
**Author:** ![pollopoop92](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a6a055/32.png) [@pollopoop92](https://www.ruby-forum.com/u/pollopoop92)\ **Post date:** [May 29, 2010, 1:07am UTC](https://www.ruby-forum.com/t/suggestion-to-design-specific-network-client/189337/3 "2010-05-29T01:07:05Z")
Il 29/05/10 00.05, Caleb C. ha scritto: > > I dont have any clue to accomplish that. I was thinkin to use > > eventmachine but i dont know if i can apply my custom setsockopts and i > > did not find any documentation about it. > > Um, maybe use threads? EventMachine ought to work too, but I can’t > speak to that. Hi again, yes i can use threads but, now i was wondering would a good idea to apply the Observer pattern in order to “fire” the other operations and keep going sampling data. > What is this sampling that you’re doing? What kind of samples are they > and more importantly, where do they come from? You’re gonna need some > kind of (hardware or software) buffering in order to ensure that no > samples get lost. The size of that buffer lets you know how long your > program can ‘go away’ and do other things (like network i/o) before > you start losing data. The samplings are UDP broadcast messages between many nodes and contain values gathered from sensors mounted in all nodes. All samples are the same, i want to collect it and after that operation create a bundle packages of collected data to another machine at regular intervals. All those nodes are into a local network. Sensor data are sent as Fixnum. I hope to be clear enough to explain my problem, feel free to ask everything, because your questions give me the opportunity to rethink about it 🙂 > HTH -Francesco ---
**Author:** ![pollopoop92](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a6a055/32.png) [@pollopoop92](https://www.ruby-forum.com/u/pollopoop92)\ **Post date:** [May 29, 2010, 4:19am UTC](https://www.ruby-forum.com/t/suggestion-to-design-specific-network-client/189337/4 "2010-05-29T04:19:36Z")
On 5/28/10, Francesco V. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > yes i can use threads but, now i was wondering would a good idea to > apply the Observer pattern in order to “fire” the other operations and > keep going sampling data. An observer feels wrong, idunno. Observer is not a thread-synchronization mechanism, AFAIK. I see 2 threads. The first gathers data and puts it into big buffers. It sends those buffers to the second thread over a Queue. The second thread waits on the Queue for buffers to come in and when they arrive summarizes them (or whatever you’re doing) and ships them out again. Probably first thread needs to be higher priority, assuming it doesn’t need to run all the time and spends a significant amount of time sleeping. > same, i want to collect it and after that operation create a bundle > packages of collected data to another machine at regular intervals. All > those nodes are into a local network. Sensor data are sent as Fixnum. > > I hope to be clear enough to explain my problem, feel free to ask > everything, because your questions give me the opportunity to rethink > about it 🙂 So in this case the lowest level buffer is the network card’s input queue. If that buffer overflows, packets will drop and you’ll lose data. This will work fine as long as you don’t max out either your network or your cpu. If either one peaks, you’ll risk data loss. Depending on how much data you’re moving around, this may or may not be a problem.