Re^5: submit to muliple actions

I understood your question of wanting to have two different scripts being invoked on the same form request, and that is not how it is supposed to happen. Yet, you can have tricks to accomplish what you want

What usually happens is that one single script is invoked and then processes and takes one or more tasks/actions. What I was trying to tell you is that could look at a means of doing your two tasks on the same script.

I don't really know your need for having two scripts, but as an example, the same script could go and read info from a database to send back to the client and at the same time log the request on a file. So these two tasks, despite being different, can be accomplished in one script instead of being processed by two separate ones.

So the point is, do you really need to have two scripts?

Comment on Re^5: submit to muliple actions

Replies are listed 'Best First'.
Re^6: submit to muliple actions by vit (Friar) on Feb 17, 2008 at 21:34 UTC
My task is even more simple. My script generates HTML for the form for another web site. Once the text is incerted in <input type=text... of this form the request is passed to this site action. My task is to pass the same string to my server with the same <input type=submit..... button and process this string on my server side.	[reply]
Re^7: submit to muliple actions by dsheroh (Monsignor) on Feb 17, 2008 at 22:24 UTC
Seems to me like it would be simpler and more straightforward to have the user's request submitted to your code, then have your code make an identical request to the other site. But it also seems likely that another approach could work better, thus going back to ikegami's suggestion that this may be an XY Problem.	[reply]
Re^7: submit to muliple actions by olus (Curate) on Feb 17, 2008 at 22:25 UTC
If it is not important which server responds to the client, you can have the form action pointing to your script. There you can do what you need to, and then post a request to the other server's script with LWP, and then send a response back to the client. If GET is used, you can issue a redirect from your scripts' response, and no more worries. If POST is used, then the redirect may cause the browser to ask users' permission to repost the form, and this may or may not be of a concern. If it is of concern, then you need to do some sort of work-around to accomplish that, and the AJAX solution could get you going.	[reply]