Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TCP HTTP Server written in Assembly

canonical.org

Post reply on HN
Print view View original

1–10 of 74 posts

Re: TCP HTTP Server written in Assembly

#2

Post by tokenizer »

As a web developer who isn't familiar with assembly or any web server more barebones than nginx, what benefits does something like this provide? Speed? Could this be a solution for an extremely simple directory/static file web server?

Re: TCP HTTP Server written in Assembly

#3

Post by hcarvalhoalves »

tokenizer wrote: post #2

As a web developer who isn't familiar with assembly or any web server more barebones than nginx, what benefits does something like this provide? Speed? Could this be a solution for an extremely simple directory/static file web server?

This is obviously a toy, or PoC.

Re: TCP HTTP Server written in Assembly

#4

Post by ars_technician »

hcarvalhoalves wrote: post #3
tokenizer wrote: post #2

As a web developer who isn't familiar with assembly or any web server more barebones than nginx, what benefits does something like this provide? Speed? Could this be a solution for an extremely simple directory/static file web server?

This is obviously a toy, or PoC.

I don't know about calling it a piece of crap. Seems a little harsh. :-)

Re: TCP HTTP Server written in Assembly

#7

Post by anonymouscowar1 »

tokenizer wrote: post #2

As a web developer who isn't familiar with assembly or any web server more barebones than nginx, what benefits does something like this provide? Speed? Could this be a solution for an extremely simple directory/static file web server?

This is a simple, single-threaded single-process accept-read-respond-loop web server. It's vulnerable to trivial trickle DoS attacks and probably has other issues. There are no advantages, the author just did this for fun.

The TCP part comes from C code in the kernel, so this headline is a little misleading ;-).

Re: TCP HTTP Server written in Assembly

#9

Post by mappu »

Cool!

My comments as an inexperienced assembly developer, assuming this is optimising for binary size:

- The pug/doN macros do an extra reg-reg copy if passed a register - and the recursive definition calls pop/pop/pop instead of just add %esp, -4*N, you could shave a few bytes

- AT&T syntax will always look weird to me, but the heavy use of macros and local labels is quite elegant

- A little bit of candid swearing in the comments? Fine by me, but is this officially associated with canonical?

Post reply on HN