[mashup-dev] [jira] Commented: (MASHUP-125) Outstanding questions on ?stub

[Jonathan Marsh (JIRA)]

    [ http://www.wso2.org/jira/browse/MASHUP-125?page=comments#action_12319 ] 
            
Jonathan Marsh commented on MASHUP-125:
---------------------------------------

Closing issue as follows:

1) no, short form is adequate.

2) single stub can be accessed in sync or async modes

3) yes, done.

4) the content-type parameter gives us a workaround

5) Too complicated for now.

> Outstanding questions on ?stub
> ------------------------------
>
>                 Key: MASHUP-125
>                 URL: http://www.wso2.org/jira/browse/MASHUP-125
>             Project: WSO2 Mashup Server
>          Issue Type: Task
>            Reporter: Jonathan Marsh
>         Assigned To: Jonathan Marsh
>             Fix For: 0.2
>
>
> Formerly flagged as notes in the Wiki spec.
> An alternative to lang=js, would be to mirror the syntax of the <script> element, e.g. "type=application/javascript".&nbsp; Is the extra verbosity worth it?
> Should we add a "form" parameter to allow various types of stubs to be generated?  E.g. a sync vs. async (as an example - currently the stubs support both) or a raw vs. RPC? Or could the "form" be embedded in the "lang" with values such as "js-raw"?
> Does the ";e4x=1" parameter constitute a media type parameter or an extension of the <script> element in Firefox?  If the former, we should append it when the lang value is "e4x".
> The media types "text/javascript" and "text/ecmascript" are deprecated by RFC 4329.  But does the use of these media types have any practical advantage?  E.g., direct display of script text in a web browser?  Need a survey of the implications here.
> Can we use content negotiation to determine the media type instead of requring and explicit request for the "lang" parameter, which may be in conflict with the requested media-type?  If content negotiation is supported in some way, it should take precedence over the lang parameter.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira