terminology

In practice, what is the most appropriate term for the communications transmitted over a network in higher level protocols (those above TCP/IP, for example)? Specifically, I am referring to small, binary units of data. I have seen both "message" and "packet" referred to in various client/server libraries, but I was interested in the community's consensus. These are definitely messages. A "packet" is a layer-3 (in ISO terminology) protocol unit, such as an IP packet; and a "datagram" is a layer-1 or layer-2 unit, such as the several Ethernet datagrams that might make up the fragments of an IP

what is a native object means i found the that java has peer class to interface with native objets? Java programs can use JNI to access to functions implemented in native code (anything compiled to machine code). Interfacing with object oriented native code requires a java class which forwards method calls from java to an instance of the native class using jni. This class is the java peer of the native class. An example: We have the print_hello class in c++ which we need to use in a java program, to do this we need to define its peer in java. The native class class print_hello{ public: void do

All over boost.org and also at other sites on the web I've seen code of this form: class whatever { ... private: std::vector<std::string> m_name; // exposition only }; What is the meaning of "exposition only"? What is the comment's purpose? What is it trying to tell me? It's used to indicate one possible way to implement the particular item, but not necessarily the best or recommended way. One of the definitions of "exposition" is: the act of expounding, setting forth, or explaining So I think they are saying that the private member (or whatever) is only shown to help you understand how the

It seems that developers often use these terms interchangeably when referring to a piece of data stored in an instance of a Class. Is there any technical difference between each term, or is it fine to use them interchangeably? "member" is broader term. It refers everything in that class (instance methods/variables etc.,) "attribute/variable/field" are same and "member" can be used too. Based on the variety of answers, Class "attributes", "fields", and "variables" are used relatively interchangeably but have nuanced distinctions that vary from person to person. As such, probably best to lump

How is exactly that we talk about "true random" numbers when we are actually measuring something. I mean, isn't measuring almost the opposite of randomness. Som articles says that, for example, throwing a dice is "true random". Of course it isn't Pseudo-random, but is it even random?? If you could have a machine that throw dices from de exactly same position and always in the same direction with the exact same force always: woudn't it always turn out the same number? (I thing it does). Please, can someone help me understand "true random" numbers?? Quantum effects are the source of this "True