• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 484 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NWP HTTP Server: Transfer-encoding: chunked

Fred Galbraith
Intellectual 610 points
Part Number: LAUNCHXL-CC3235SF

Hello,

I see that the NWP HTTP server does not include the field "Transfer-encoding".  Therefore, I don't think I can send chunked data with it.  Chunked data is great for embedded applications because the entire size of the page does not need to be calculated/known ahead of time.

Is that the case?  If so, would TI entertain building in this feature in a future release of the NWP server?

Thanks!

  • 0
    TI__Mastermind 38980 points

    Hi Fred,

    The local_ota example uses the internal NWP HTTP server and accepts the image payload in chunks, but I'm not sure about the use of that header field.

    The HTTP server application library does generate that response header field, and then it looks like the application chunks the data.

    Best regards,

    Sarah

  • 0 in reply to Sarah P
    Intellectual 610 points

    Thanks, Sarah.  You're right, I do feed the NWP server in pieces, and it works well.  However, I need to pre-calculate the total size of the HTML file which is a lot of extra memory and time (i.e., the initial Content-length field must be filled-out).

    If TI supported the Transfer-encoding field, chunked support would improve quite a lot.

    Cheers!

    Fred.

  • 0 in reply to Fred Galbraith
    TI__Mastermind 38980 points

    Hi Fred,

    Understood. I can note the request for future releases, but I'm unable to provide any commitment on it. I will let you know that typically new HTTP server feature requests are redirected to the application library instead of patches to the internal NWP.

    In your application, are you using sl_NetAppSend or the SimpleLinkNetAppRequestEventHandler response? Does your application have low power constraints?

    Best regards,

    Sarah

  • 0 in reply to Sarah P
    Intellectual 610 points

    Hi, Sarah,

    Thanks so much.   In my application I am using both SimpleLinkNetAppRequestEventHandler and sl_NetAppSend.  I am using the framework used by the local_ota reference design.  It seems to be working fine so far.  I am able to create custom pages with text, graphics, javascript.  

    I do not have low power constraints, though in the future I think battery power should be an option for the product.

    Cheers,

    Fred.

  • 0 in reply to Sarah P
    Intellectual 610 points

    By the way, I found that if the Content-Length AND Transfer-encoding fields are omitted from the HTML header, then the connection simply needs to be closed at the end to terminate the transfer.  I am using this technique and it is working fine on multiple browsers.  So, it appears that chunked transfer is not required if the connection is simply closed.