On Wed, Aug 13, 2008 at 4:33 AM, Komяpa <[EMAIL PROTECTED]> wrote:
> I'd like to know something about ntkd development status. Is python
> implementation working at the moment? Will it have all the features of old C
> ntkd? Are there plans to finish / stabilize the code / protocol by certain
> date?

That's been an old question since very long time ago: we don't know.

It depends entirely to the free time the devs have, and there is only a few
bits we can do about it:

 * Either code and submit patches
 * Or help with everything that isn't code (documentation, web site, mailing
   lists, IRC, but mostly documentation)

pyntk is evolving, so it will have the same features that the old C
implementation
had and more. In fact, the features are documented in the main_doc category.

>  - It lacks support for messengers. NTK network in first will fall apart very
> frequently (AP switched off, dead internet connection for Viphilama). It could
> leave a region without an irc/jabber/mail server. In my opinion it's possible
> to write distributed irc/mail server implementation that will be able to
> survive after LHC startup. :)

The p2p bits are already on the code, it just needs to be finished. However,
there is also a project to bring decent p2p bindings that use the ntk network
at it's glance, but it will come later when the new pyntk code stabilizes.

IMO, it will be a good idea, but I rather see pyntk working first :>

>  - Windows support. I know that linux is better, but here in Belarus m$win is
> installed on 90% of computers. Something should be done. :)

Directly from the FAQ:

"Q: Will Netsukuku be ported to Windows?
A: Short answer: if you code the port, yes.
   Answer: We need coders for that. There are a lot of things to be done and
   the Windows port is what we care less."

>  - APs. Old C implementation was able to run on APs. New one depends on
> stackless python. There's only 1 mb of flash and 1-2 mb of free ram available
> on most APs, which is defenetely not enough. That's why I think that routing
> core should be rewritten in C.

You can get a stackless python binary under the 1mb limit. You just need to
strip off everything you don't need from the original distribution.

-- 
Ricardo Lanziano
6838 E880 7CA4 D4B6 8283 8F65 96AD EC0B F113 AB62
Unix is simple. It just takes a genius to understand its simplicity.
_______________________________________________
Netsukuku mailing list
[email protected]
http://lists.dyne.org/mailman/listinfo/netsukuku

Reply via email to