>From the livedocs for URLRequest: If the object is a URLVariables object and >the method is POST, the variables are encoded using x-www-form-urlencoded >format and the resulting string is used as POST data.
So do that rather than sending them in the query string. There's no general size limit on the body of a POST, and the HttpServletRequest parameter map gives you access to parameters sent either in the query string or in a POST body when they're encoded this way. You don't need to deal with the request object's input stream directly. Seth From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of schneiderjim Sent: Friday, August 29, 2008 12:00 PM To: [email protected] Subject: [flexcoders] Re: Where is URLRequest data on server side Thanks Seth. The problem is that I have a large (and growing) number of parameters (or rather, a large number of characters in the parameters) and I think I'm exceeding the limits of the HTTP query string/parameter map (I was thinking the limit was 256 or 1024 depending on get vs post). More specifically, I have a grid that I want to throw into a PDF. I use JasperReports on the backend. So, my first solution was to send the object "IDs" from the grid to the server, have the server do a bulk query, and then have JasperReports return the PDF. The problem now is that the list of IDs is growing and the actual number of characters is increasing. For example, the IDs used to be "1,2,3,...", now the are "100000,100001,100002, ....". In the URL to my servlet, I do the following: <myurl>?ids=1,2,3 now <myurl>?ids=100001,100002,100003 And so on. When I experience the issue, it's as if the request never even gets out the client, although I have yet to track that down (doing that now). I could change the parameters list to just send the search criteria (which generates the list/grid in the first place), but there is also some filtering involved, and I had hoped to not need to recreate the search/filter logic again on the server side. Thanks --- In [email protected], Seth Hodgson <[EMAIL PROTECTED]> wrote: > > Hi Jim, > > Be sure to set your request.method = URLRequestMethod.POST and assign your URLVariables to the data property of your URLRequest and then pass that to navigateToURL(...). > > On the server, you can access these name/value pairs as request parameters (HttpServletRequest#getParameterMap()). > > Using navigateToURL() is the right way to do this. > > Seth > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of schneiderjim > Sent: Thursday, August 28, 2008 10:02 AM > To: [email protected] > Subject: [flexcoders] Re: Where is URLRequest data on server side > > > Bump. > > --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, "schneiderjim" <jschneider@> wrote: > > > > I'm using URLRequest and navigateToUrl to invoke a server side (java > > servlet) reporting function (returns PDF in new browser window). To > > get it to work quickly, i just attached HTTP parameters to the URL and > > grabbed them from the HTTPServletRequest on the server. However, I > > believe we are now hitting the limit on the "query string", and I'd > > rather not do this anyway. > > > > I've looked at the URLVariables and the data property and that seemed > > like what I should do, but on the server, I'm not sure where I would > > grab that data in my servlet. Does that come through the InputStream > > somehow? > > > > Would HTTPService be better (noting that I need to pop the resulting > > PDF into a new window)? > > > > Any pointers to docs or samples would be appreciated. > > > > Thx, > > > > Jim > > >
