Making a webserver

[poymode]

---

if you were to make a webserver, how can you make it different from the others?

-are there any areas where you could improve it?
-are there any areas where it lacks something that you might add something to it?
etc etc

pang thesis ni..hehehe

[simoncpu]

if you were to make a webserver, how can you make it different from the others?

-are there any areas where you could improve it?
-are there any areas where it lacks something that you might add something to it?
etc etc

pang thesis ni..hehehe

I dunno... existing web servers are OK. You can try writing a lightweight server that you can use in embedded applications, with focus on speed and simplicity.

Examples of lightweight web servers are lighttpd, thttpd, and nginx. Maybe you can try writing a server using Java so that you can run it in your PDA/Smartphone (I'm not of the opinion that Java itself is lightweight, but what the heck... hehe).

BTW, asa ka nag-iskul?

[softtouch]

What could you probably make better than apache already is?

[simoncpu]

What could you probably make better than apache already is?

Well, you can make it lightweight because Apache eats up too much memory. It is not suitable for embedded appliances.

It is also slower than lighttpd and nginx, that's why it's not the best choice for high-traffic sites. lighttpd is used on YouTube, Wikipedia and Meebo. nginx is used on YouP0rn. Hehehe.

[ simon.cpu ]

[ChaosOrb]

make your webserver open source and platform independent.

[BeoR]

You can always recompile apache without the modules that you do not need... and apache has pretty much caught up with lighthttpd in terms of speed nowadays.

[simoncpu]

You can always recompile apache without the modules that you do not need... and apache has pretty much caught up with lighthttpd in terms of speed nowadays.

Probably, but if you watch the Apache processes carefully, the memory consumption is hundreds of MB per process.

You can probably tweak the config to match lighttpd and nginx, but the performance won't be the same. It started as "a patchy server" after all...

[BeoR]

Performance-wise they are practically the same... memory consumption is irrelevant, you should look at the number of requests it can handle / process. They all have their pros and cons.

[bigeasy]

I wish Apache installs with a bare bones install then allows you to add modules that you need, instead of the other way around. I switched my servers to Nginx and never looked back.

Back to the original topic... make it Fast and Free.

[simoncpu]

Performance-wise they are practically the same... memory consumption is irrelevant, you should look at the number of requests it can handle / process. They all have their pros and cons.

That's only true with certain hardware, and with certain needs. For a website such as istorya.net, Apache is probably OK. With certain applications, however, it is not:

http://picasaweb.google.co.uk/simonc...50150989666146

Have a nice day!