GitHub user dcristoloveanu opened a pull request:

    https://github.com/apache/qpid-proton/pull/25

    Initial transport frame size 256 bytes

    In order to reduce RAM footprint on rather simple scenarios on small 
devices the initial transport frame size could be lowered to 256, since the 
buffer is anyhow automatically enlarged if needed.
    
    Per earlier suggestions I created a config.h where parameters like this can 
go (the next candidate is the initial size for pn_data). If the need arises 
these parameters should be easily changeable in this case to match the platform 
need.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dcristoloveanu/qpid-proton 
RAM-Transport-Frame-256-bytes

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton/pull/25.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #25
    
----
commit 2158ef3447bab718cfa7b1cb9f9c635cb83beb7f
Author: dcristoloveanu <dcri...@microsoft.com>
Date:   2015-04-28T21:01:49Z

    Add config.h

commit 65c6ce3df2c1c531cce49d2c3aab5f79f59c63bb
Author: dcristoloveanu <dcri...@microsoft.com>
Date:   2015-04-29T21:21:31Z

        -Added a configuration file named config.h where various parameters 
should be configurable (like transport initial frame buffer size, pnin the 
future _data initial size, etc.)
    
        -Set initial transport frame buffer size to 256 instead of 4K
        -Added config.h to the cmakelists.txt so that it shows up also in the 
Proton.sln Windows solution

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to