Hi, > Here are the various ways the open function can be called > > open(httpMethod, url, async); > open(options, url, async); > open(httpMethod, url, username); > open(options, url, username); > > open(httpMethod, url, username, password); > open(options, url, username, password); > open(httpMethod, url, async, username); > open(options, url, async, username); Above are done according to the WSRequest specification designed by the WSRequest ActiveX/Native guys (Supun, James,etc..) some time back. It was in the old wso2 wiki, I'm not sure where it lies today.
Above can be rewritten as open with many optional parameters, as it is with many javascript functions.. From the http://wso2.org/wiki/display/mashup/WSRequest+Host+Object 2.1 WSRequest Interface.. void open ( in object options | in String method, in String url [, in boolean async [, in String user [, in String password]]]); "|" stands for "OR".. Parameters inside square brackets are optional.. But I'm not sure how usefull those are.. thanks, Thilina > > > This looks a bit too complex for me (even when you think of documenting > this). > > The only thing thats documented is open(options, endpointAddress, > async). I propose moving httpMethod, username and password to options. > So that we basically have just open(options, endpointAddress, async) > > WDYT? > > Note: Username and password is currently used for HTTP Basic Auth > > Thanks, > Keith. > > _______________________________________________ > Mashup-dev mailing list > [email protected] > http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev > _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
