On 8/04/2016 6:34 PM, Sebastian Huber wrote:
On 08/04/16 04:22, Chris Johns wrote:
On 8/04/2016 12:37 AM, Joel Sherrill wrote:
Chris and I have discussed at least some of the network services being
considered packages beyond the stack. Stuff like httpd, ftpd, and
telnetd should be able to work with either stack. Having one instance of
those to maintain would be great.
I'm happy to see all this happen. Hopefully it can show up in digestable
pieces.
We need to maintain our current functionality and I am prepared to
bridge but not abandon. The libbsd stack has made progress but does
not support as much as the old stack does. Until it does I feel we
need to keep the old stack going and to support it.
The old stack is still a valid option since it uses considerably less
memory than the new stack.
I agree.
To me this means adding headers to newlib requires the in-tree stack
and libbsd work with out impacting users and existing applications.
If I understand what is bring proposed any suitable networking
software should be able to be built against just the compiler, newlib
etc and it does not need a built and installed RTEMS with a specific
networking implementation. This means networking could become a link
time setting. An interesting challenge.
Yes, this is the goal.
Awesome.
Sebastian, I know you have talked about libressl, but it is still not
clear to me why doing this is needed. Do you have a specific use case?
Its not needed, but would simplify things.
Great.
We want to update the
mongoose HTTP server to support HTTPS.
Does this mean we have forked mongoose? Maybe it needs to be called
something else if this happens.
We also want to use it with the old and new stack.
This is great.
Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
