From: Zoran V. <zv...@ar...> - 2005-06-16 21:05:24
|
Am 16.06.2005 um 22:52 schrieb Vlad Seryakov: > > When you call ns_queryget/ns_getform, NS parses the input and split > content into temporaty file in case of attachements. When sending > multipart/data content and i called ns_queryget at the beginning of my > connection script, parser needs all the data available, big > attachments can be the first one and other query parameters at the > end. How lazy > parsing will happen? Will my ns_queryget wait while the content > is being downloaded? Lets see if I understand... You can check ns_conn contentlength in advance and decide to get all the content or to discard it (because too large). You can use ns_conn setmaxinput to some large(r) value and then call ns_queryget. The ns_queryget will call Ns_ConnContent and this is now clever to either return the content from memory (if < maxreadahead) or do more complex stuff by mapping file and sinking all the content in a memmaped file. The returned byte array for futher parsing would be just from the mmaped file. The callers of the Ns_ConnContent will not see the difference. Stephen, did I got it right? Zoran |