You could send back a form to the client whose action attribute points to
the other application with method="post" and all the parameters you need to
submit embedded as hidden inputs. You could then allow the user to submit
the form manually or you could submit it automatically with Javascript. This
allows you to pass all the information as request parameters without
worrying about URL length.
Never tried it, but it might work.
-Ben
On Wed, Feb 4, 2009 at 11:17 AM, kriko <[email protected]> wrote:
> Hello!
>
> I've made 2 applications based on stripes framework.
> The first one retrieves some data from one service (user location or
> multiple locations), the second is obligated to display data on a map.
>
> Both are deployed on localhost for now and they are working separately, but
> now I would like to connect
> them.
>
> What would be the best approach? I tried to do a ForwardResolution from
> first one, but that doesn't work.
> What if they are deployed at the end on different servers?
>
> There can be lot's of points, so I'm not sure if it is ok to pass this via
> URL parameters.
>
> --
> kriko
>
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
