| Re: [cf-dev] Counting the number of bytes traveling between device and server |
|
Thank you Matthias that will give me a good place to start trying to understand Californium.
So, can I start working on this requirement? Regards Vinay From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kovatsch Matthias Hi Not yet. A simple way to realize this would be to use a MessageInterceptor: It is basically a hook mechanism that is able to see all messages that go in or out of an endpoint (including duplicates etc.). The
MessageTracer.java,
for instance, simply provides pretty prints. Depending on your use case, we might need to extend it with a hook for invalid messages (i.e., data that cannot be parsed to a CoAP message). BTW: I still have another MessageInterceptor on my ToDo list, that logs the number of different peers for the Eclipse statistics. Ciao Matthias From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Gajjala Vinay Hi All, Currently I am working on the device server and external facing server which implements multiple protocols and one of them is the LwM2M. We are
in the process of collecting the number of bytes that travel between server and the device and store it in the database for later use. I would like to know if there is a way to get this information from the californium. I have asked this question to Julien
of Leshan project and he mentioned that this is a Californium question. In case if this feature is not available, I am interested to work on this. Help is much appreciated. Best Regards Vinay This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole
or partial, is prohibited. This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus. |