Re: Tux API question: post_data
Bojan Smojver <[email protected]>
| Newsgroups | gmane.network.tux |
|---|---|
| Message-ID | <[email protected]> |
I was reading the one from here: http://people.redhat.com/mingo/TUX-patches/modules-docs/TUXAPI-user.txt Can you point me to the correct version? Thanks, Bojan On Sat, 2002-04-06 at 02:53, Craig McLane wrote: > Bojan, > What version of the documentation are you reading. The latest > versions of tux(2) have it correctly documented as a pointer. If it > is another piece of documentation then it should be corrected. > > Craig > > > On Fri, Apr 05, 2002 at 11:36:39AM +1000, Bojan Smojver wrote: > > 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 > > > > > > > > _______________________________________________ > > tux-list mailing list > > [email protected] > > https://listman.redhat.com/mailman/listinfo/tux-list > > > > _______________________________________________ > tux-list mailing list > [email protected] > https://listman.redhat.com/mailman/listinfo/tux-list >