Re: [wsrp-markup] [wsrp][markup] Minutes for 7/10/02 conference call

[Chris Braun <cbraun@silverstream.com>]

Mike,

 

Well the sad thing is that I can't explain it, I have to admit I was a bit confused on the call.  The more that I think about it, it seems that in order to incorporate this functionality the WSRP interface protocol would need to allow for this.  The consumer would probably need to determine weather the action should be sent to the producer or simply a getMarkup call along with the parameters.

 

This seems like something the interfaces subcomittee will need to decide.  If you guys decide that this is a required part of the protocol then the url rewriting will have to incorporate some kind of mechanism to indicate to the consumer what path to take.  Has this been discussed in the interface subcommittee yet?

 

Chris

----- Original Message -----

From: Michael Freedman

Cc: WSRP-Markup

Sent: Thursday, July 11, 2002 4:17 PM

Subject: Re: [wsrp-markup] [wsrp][markup] Minutes for 7/10/02 conference call

Chris,
   Sorry I missed the call this week.  Can you explain why:

 JSR 168 has the notion of action URLs and render URLs.  An action URL causes an entity to execute its process phase.  By allowing two types of actions the entity can bypass the action phase and allow for the render phase to receive the action parameters.  There is probably nothing that needs to be added to the WSRP protocol to address this.  The producer container will be able to handle this transparently.
 

   How does the container/portal determine whether to call the action method vs. the render method if there isn't an indication in the originating URL?  I.e. how is this handled transparently?  Are we expecting the JSR to encode this information in "query string" parameters - hence its opaque to us?
      -Mike-