Re: [NTLK] App porting

On Wed, 22 Jul 2009 20:45:54 -0500, Joshua Armenta <josharmenta@gmail.com>
wrote:
> The reason I would be interested in attempting this build would be for
> the native SSL implementation in firefox;

Some caveats: The NewtonOS does not use sockets internally at all, but an
architecture modeled after OpenTransport, which is modeled after STREAMS.
It's in principle more powerful, but also makes porting more difficult.

The other issue is that the C++ compiler of the NCT is quite old, and might
not be able to compile more recent C++ code. Plus, it does not like any
global variables.

The last thing which makes this a bit tricky is to expose the SSL
implementation properly to the NewtonScript layer, and this is probably the
biggest hurdle, because it requires reverse engineering NIE. The
alternative is to reimplement NIE ;)

I'm not sure what the state of the art regarding memory consumption is with
the latest rendering engines, but the Newton only has about 1MB free
dynamic RAM.

Overall, if you start with the crypto librabries needed by SSL, that would
be already a very nice achievement.

Eckhart

-- http://40hz.org

====================================================================
The NewtonTalk Mailing List - http://www.newtontalk.net/
The Official Newton FAQ - http://www.splorp.com/newton/faq/
The Newton Glossary - http://www.splorp.com/newton/glossary/
WikiWikiNewt - http://tools.unna.org/wikiwikinewt/
====================================================================
Received on Thu Jul 23 04:23:29 2009