Posted by Jim Guerber on March 27, 2009 at 12:15:56:
In Reply to: XAP Maximum Variable Length posted by Jon Sacks on March 27, 2009 at 10:03:10:
Jon, It is not totally clear, but what I understand you are doing is receiving a post from a "browser" into your xap system. Xap parses the post into several usable pieces that it writes as records into the keyed file that drives your programs. It splits up query data into meaningful chunks with the keys Q.zzz where zzz is the query key. Each of these records is 1024 bytes long. You may read them into comet variables with a format that will accommodate that amount of data.
If your query records only accommodate 254 bytes, its a bug. Let me know so we can set up a test.
Alternatively, If you are dealing with POST data (POST data only, please, because GET data was meant to be strings of relatively small size), we also write the entire post into records in the file with keys such as P.00, P.01 etc. These records are each 1024 bytes in length. Look at the tutorial link below, and click on the cgitest button. Notice the P.00 record. If you use the P.xx records, you may parse the whole POST yourself instead of relying on XAP to do it.
We are in the midst of implementing the next version of XAP at this time. We are very open to suggestions for improvements.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.