Re: [lwip-users] SSH - Raw API

2017-03-10 Thread Noam Weissman
: lwip-users@nongnu.org Subject: Re: [lwip-users] SSH - Raw API As long as you have the memory and CPU resources, you can have an RTOS and as many threads as you can, with all the apps you need. lwIP main core and RAW API apps will run on a thread, other apps with their netconn/socket APIs on their respec

Re: [lwip-users] SSH - Raw API

2017-03-10 Thread Sergio R. Caprile
As long as you have the memory and CPU resources, you can have an RTOS and as many threads as you can, with all the apps you need. lwIP main core and RAW API apps will run on a thread, other apps with their netconn/socket APIs on their respective threads. The point is... do you actually

Re: [lwip-users] SSH - Raw API

2017-03-10 Thread Sergio R. Caprile
It is not a matter of possible/impossible, but how much are you willing to thrive to do it. Unless you do it yourself from the RFCs, you'll work with already made parts, which most probably have been written for a socket(-like) API, most probably on a non event-driven way. You'll find some

[lwip-users] SSH - Raw API

2017-03-08 Thread nrichard
Hello everyone, I was wondering if it's possible to have an SSH server using LWIP's Raw API. I saw there's a shell app in the contrib files that uses the netconn API, but my project (http server, snmp server, ftp server) have all been entirely raw API, and I would like to keep it that way. Or