The other good (IMHO :-) suggestion that you received in earlier responses was to store the bulk of the data you want to transport in a database somewhere that is accessible to both the "from" and "to" applications. Then, all you have to send along in the URL would be a single request parameter that contains the primary key into the table so that the destination application can pull out what it wants.OK - I can see how using cookies in this case is less than desirable.... (thanks Craig)
So, am I just screwed? The problem with returning data on the query string is that I can easily exceed the 2k limit; using session variables won't work either because I can be called from separate instances of Tomcat or even IIS running on distinct servers. And because of this, I have to use response.sendRedirect() which means I can't put objects in the request.
Any other ideas?
This is sort of like simulating a session across different applications, but it would get the job done.
If the database is too complicated, just make sure your requests to the destination server will be POSTs of a <form> instead of GETs. Then, you can include as much data as you need as hidden variables inside the form.
Jerry JalenakCraig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
