Tux API question: post_data

I've noticed that structure user_req_t contains post_data as a char
array of a finite length MAX_POST_DATA. This might be practical for
'normal' post operations, but what if someone is doing
multipart/form-data and is uploading a file? Wouldn't it be more
practical to have a pointer (i.e. char *post_data) and then the length
of the actual post (i.e. size_t post_data_len) or something? The memory
for each post would then be allocated dynamically too.

Or maybe I just misinterpreted the whole thing...

Bojan