OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [wsrp-wsia] [I#196] Consumer can not force consumer rewriting tobe used for URLs


Lets think through the scenario to see where it could break:
 1) The Consumer defines its template in such a manner that Consumer URL 
writing is used 
              [fragment => 
...&wsrp-navigationalState={wsrp-navigationalState}]
 2) Producer stores this template in its markup for embedded javascript to 
use 
              [fragment => 
...&wsrp-navigationalState={wsrp-navigationalState}]
 3) Consumer finds the embedded template and rewrites it
              [fragment => ...&ns={wsrp-navigationalState}  or 
/ns_{wsrp-navigationalState}/]
 4) JavaScript runs and replaces the Producer supplied values
              [fragment => ...&ns=fooBar  or  /ns_fooBar/]
 5) URL is activated for Consumer processing


To me this looks like it works provided:
  1. Consumer finds/replaces "&wsrp-navigationalState=" and does not touch 
{wsrp-navigationalState} => worth mentioning in the primer to avoid 
Consumer bugs in this area.
  2. Producer never breaks up a template when storing it for client side 
JavaScript use. This would be a dangerous thing to do anyway and therefore 
merits a mention in the primer as well.

I am starting to wonder if we are gathering enough of these types of 
things that we should consider a "Best Practices" document as well. We 
certainly should be using a separate portion of the primer from the 
tutorial until we are ready for splitting in this manner ....

Rich Thompson




Carsten Leue <CLEUE@de.ibm.com>
01/08/2003 03:58 AM
 
        To:     Eilon Reshef <eilon.reshef@webcollage.com>
        cc:     wsrp-wsia@lists.oasis-open.org
        Subject:        RE: [wsrp-wsia] [I#196] Consumer can not force 
consumer rewriting to be used for       URLs



Hi Eilon.

Can you detail on this. I think I do not understand why the approach to
provide ANY tempalte (including the one that results in consumer 
rewriting)
should not work for the javascript code. That would worry me.


Best regards
Carsten Leue

-------
Dr. Carsten Leue
Dept.8288, IBM Laboratory Böblingen , Germany
Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401



 
             Eilon Reshef 
             <eilon.reshef@web 
             collage.com>                                               To 

                                       wsrp-wsia@lists.oasis-open.org 
             01/07/2003 07:59                                           cc 

             PM 
                                                                   Subject 

                                       RE: [wsrp-wsia] [I#196] Consumer 
                                       can not force consumer rewriting to 

                                       be used for URLs 
 
 
 
 
 
 




This could be a great way to test WSRP initially. To the best of my
understanding, though, such a technique would not necessarily be 
applicable
to real-life situations. For example, if a Producer has JavaScript that
executes document.location.href = url; and the Producer takes care to
create a proper JavaScript (which takes into account the provided
templates), then providing the Producer with a dummy template is not
guaranteed to work. (I.e., we rightfully don't demand Producers to support
this hack ;-)
      -----Original Message-----
      From: Rich Thompson [mailto:richt2@us.ibm.com]
      Sent: Thursday, January 02, 2003 8:26 AM
      To: wsrp-wsia@lists.oasis-open.org
      Subject: Re: [wsrp-wsia] [I#196] Consumer can not force consumer
      rewriting to be used for URLs



      It is quite easy to supply a default template that results in
      Producer URL
      writing outputting the format for Consumer URL rewriting.


      Rich Thompson







      Gil Tayar <Gil.Tayar@webcollage.com>
      12/18/2002 04:04 AM

              To:     wsrp-wsia@lists.oasis-open.org
              cc:
              Subject:        [wsrp-wsia] [I#196] Consumer can not force
      consumer rewriting to be used for       URLs





      Issue: 196
      Status: Active
      Topic: user_info
      Class: Minor_Technical
      Raised by: Andre Kramer
      Title: Consumer can not force consumer rewriting to be used for URLs
      Date Added: 18-Dec-2002
      Document Section:   v0.85/9.2
      Description:
      In the 1.0 timeframe, it would be good, for testing and bug work
      arounds,
      to allow the consumer to not supply templates to a producer which
      indicates "doesURLTemplateProcessing", so that consumer URL 
rewriting
      is
      forced to be used. [Spec says consumer MUST supply templates but all
      URL
      templates are nilable or minOccurs="0".]
      Resolution:





      ----------------------------------------------------------------
      To subscribe or unsubscribe from this elist use the subscription
      manager: <http://lists.oasis-open.org/ob/adm.pl>





----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC