[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [leshan-dev] Correct usage of blockwise transfer from server to client
|
Try
https://github.com/eclipse/californium/blob/2.0.x/californium-core/src/main/java/org/eclipse/californium/core/network/config/NetworkConfig.java#L132
Mit freundlichen Grüßen / Best regards
Achim Kraus
(INST/ECS4)
Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY | www.bosch-si.com
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn
-----Original Message-----
From: leshan-dev-bounces@xxxxxxxxxxx [mailto:leshan-dev-bounces@xxxxxxxxxxx] On Behalf Of durandal74@xxxxxx
Sent: Sonntag, 23. Juli 2017 19:26
To: leshan developer discussions <leshan-dev@xxxxxxxxxxx>
Subject: Re: [leshan-dev] Correct usage of blockwise transfer from server to client
Hi Achim,
thank you so much for that hint, it works! I increased the value of MAX_RESOURCE_BODY_SIZE. Before I read your message I only changed the value of MAX_MESSAGE_SIZE whithout success. Do you know if there is a documentation available for the properties used in the Californium.properties file? I couldn't find one online and the difference between, lets say MAX_RESOURCE_BODY_SIZE and MAX_MESSAGE_SIZE seems not very self-explanatory to me.
Your assumption is right regarding the use of big size payloads: I am actually using Raspberry Pis for development right now, since I am not very familiar with app development for constrained devices ;).
Best regards,
Sebastian
Am 14.07.2017 um 10:04 schrieb Kraus Achim (INST/ECS4):
> Hi Sebastian,
>
> Leshan 1.0.0-M3 refers to californium 2.0.0-M3.
>
> So let's start with the blockwise transfer configuration:
> - for californium 2.0.0-M3 the largest blockwise payload (at least in transparent blockiwse mode)
> is configured using MAX_RESOURCE_BODY_SIZE.
> Depending on you run the leshan demos or your own code, this must be either ensured by editing
> the "Californium.properties" file (best practice: rename it, start the server or client, merge the new
> file with potential new configuration values and then adjust the new values to your requirements)
> Other value PREFERRED_BLOCK_SIZE and MAX_MESSAGE_SIZE may also be adjusted to
> your needs. Please note, that you should do this on both sides, client and server.
> If you use your own code, you either also use:
> builder.setNetworkConfig(NetworkConfig.getStandard());
> the it should be the same. Or you must provide the adjusted configuration using
> builder.setNetworkConfig(yourConfig);
>
>> I can only guess that blockwise transfer is more common from client to server when reading whole objects or during discover operations. Does this differ from my use case?
> FMPOV having a "blockwise transfer" on a constrained device is somehow a contradiction.
> If your device is really constrained, this mostly requires a "trick"
> (e.g. reading direct from flash) and therefore in my opinion only works for a "user-defined object with a "plain opaque" resource read with the content type application/octet-stream".
> Using TLV on the fly maybe much, much harder. Therefore reading
> "objects" (all instances as once using TLV) is more a very optimistic use-case or something for "none" constrained devices as "android phones" or "raspberry PI".
>
>
> Mit freundlichen Grüßen / Best regards
>
> Achim Kraus
>
> (INST/ECS4)
> Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332
> Waiblingen | GERMANY | http://www.bosch-si.com
>
> Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411
> B
> Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung:
> Dr.-Ing. Rainer Kallenbach, Michael Hahn
>
>
>
> From: leshan-dev-bounces@xxxxxxxxxxx
> [mailto:leshan-dev-bounces@xxxxxxxxxxx] On Behalf Of durandal74@xxxxxx
> Sent: Donnerstag, 13. Juli 2017 22:42
> To: leshan developer discussions <leshan-dev@xxxxxxxxxxx>
> Subject: Re: [leshan-dev] Correct usage of blockwise transfer from
> server to client
>
> Hi Achim,
> I'm currently using the latest release version 1.0.0-M3. From what I've read so far, inquiries on mailing list and bugs (see below links marked with *), I thought this to be a quite straightforward task. One object which uses such a functionality should be the firmware object, but I have not found any implementation of it yet. I can only guess that blockwise transfer is more common from client to server when reading whole objects or during discover operations. Does this differ from my use case? Do you have any suggestions for correctly setting up Californium?
> Best regards,
> Sebastian
> *https://dev.eclipse.org/mhonarc/lists/leshan-dev/msg00337.html
> *https://bugs.eclipse.org/bugs/show_bug.cgi?id=471101
> *https://github.com/eclipse/leshan/issues/302
> Am 10.07.2017 um 10:02 schrieb Kraus Achim (INST/ECS4):
> Hi,
>
> depending on the leshan version your using, this may require some setup for californium.
> So which version you are talking about?
>
> Mit freundlichen Grüßen / Best regards
>
> Achim Kraus
>
> (INST/ECS4)
> Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332
> Waiblingen | GERMANY | http://www.bosch-si.com
>
>
> Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411
> B
> Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn
>
>
>
>
> From: mailto:leshan-dev-bounces@xxxxxxxxxxx [mailto:leshan-dev-bounces@xxxxxxxxxxx] On Behalf Of "Markus Müller"
> Sent: Freitag, 7. Juli 2017 20:32
> To: mailto:leshan-dev@xxxxxxxxxxx
> Subject: [leshan-dev] Correct usage of blockwise transfer from server
> to client
>
> Hi everybody,
> I am searching for help regarding the usage of blockwise transfer from a Leshan server to a Leshan client.
> I am trying to transfer an opaque message from a Leshan server to a Leshan client whose size exceeds the maximum size for one single package. Therefore the client returns a 4.13 message indicating that the message size is too big. I was of the opinion that the BlockwiseLayer would take care of the blockwise transfer if the message is too large for a single message. When sending messages via the WriteRequest I see no interface for manipulating the block options. Therefore I assume it's not intended to set these on the lwm2m layer. Did I miss some configuration value? Any help is appreciated!
> Best regards,
> Sebastian
>
>
>
> _______________________________________________
> leshan-dev mailing list
> mailto:leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/leshan-dev
>
> _______________________________________________
> leshan-dev mailing list
> leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/leshan-dev
