Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lfroen]

Recently I have finally succeeded to compile amuled for NSLU. It works great, but unfortunately amuleweb have a problem. The problem is memory consumption.
Since amuleweb is separate application, it mirrors amule datastructure in some way. In turn, amule core, also mirrors some part of it's own datastructure to enable differential data exchange. All this mirroring is needed to minimize bandwidth and CPU time needed.

There's a way to minimize total memory footprint of amuled+amuleweb - compile them together as one application. This can be chosen as configure-time option, like --enable-monolitic-webserver.

[lfroen]

1) This have nothing to do with existing EC (meaning it stays as-is)
2) Possible

[Kry]

Funny how years ago we separated them to now have them together again.

[lfroen]

Funny how years ago we separated them to now have them together again.

I can see some advantages of separation, but on embedded system with limited memory (NSLU is good example) it's better to have them together. That's why it's optional

[skolnick]

One advantage of separation is that you can choose what to install, and what not. For example, I only need amule monolithic and amuleweb (I don't install amuled, alulegui, nor amulecmd), but other people might need only amuled and amulecmd, so they would not need what I need. Modularity is a great thing.

Regards.

[lfroen]

One advantage of separation is that you can choose what to install, ...
Modularity is a great thing.

Yes, modularity is great thing. I would argue, however, that modular design is great thing, but not necessary modular distribution, but this is debatable.
In order to save myself from this discussion, which is gonna be anything but productive, I will preserve existing setup, and add new one as configure option.
As part of change, http socket in amuleweb will become non-blocking, which is good by itself and should be made time ago.