Re: Make p:http-request required?

/ Norman Walsh <ndw@nwalsh.com> was heard to say:
| / Jeni Tennison <jeni@jenitennison.com> was heard to say:
| | Alex Milowski wrote:
| |> On 4/30/07, *Norman Walsh* <ndw@nwalsh.com <mailto:ndw@nwalsh.com>> wrote:
| |>     I propose that we move [p:http-request] to the "required" pile.
| |>
| |> + 1 to that!!!
| |
| | Are there any security considerations that we need to worry about?
| |
| | I don't really understand how p:http-request works (as in the 30th April
| | draft). It doesn't seem to be a standard atomic step, since it has
| | attributes that correspond to options.
|
| Ah. True. Those things probably ought to be options.

Oops. Brain cramp. The method, href, status-only, and override-mimetype
*attributes* are on the ***c***:http-request element, not the step.

That element is expected to be the document element of the request
sent on the input port.

Having p:http-request and c:http-request may be asking for trouble.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/            | possible, but no simpler.