Hi Dilan,
Please find my comments inline.
Can you explain the use-case behind splitting onRequest() function to two,
> i.e. onGet() and onPost() ?
>
Please refer mail thread[1] for this.
> Does this mean that we can have independent server-side JS scripts in UUF
> to handle a GET or a POST
Hi Folks,
Can you explain the use-case behind splitting onRequest() function to two,
i.e. onGet() and onPost() ?
Does this mean that we can have independent server-side JS scripts in UUF
to handle a GET or a POST outside pages and units ?
Thanks.
Dilan.
*Dilan U. Ariyaratne*
Senior Software
>
> IMO, we don't need PUT, DELETE for serving web pages. PUT & DELETE are
> needed for a REST API, and UUF has a way to deploy microservices for REST
> APIs. So I don't see a requirement for 'onPut', 'onDelete' functions in
> server-side JS.
+1, Adding PUT, DELETE will mislead the fundamental
IMO, we don't need PUT, DELETE for serving web pages. PUT & DELETE are
needed for a REST API, and UUF has a way to deploy microservices for REST
APIs. So I don't see a requirement for 'onPut', 'onDelete' functions in
server-side JS.
On Wed, Jan 25, 2017 at 10:48 AM, Lakshman Udayakantha
Hi Shan,
Shouldn't we add functions like onPut() , onDelete() for other HTTP methods
like PUT, DELETE?
Thanks
On Wed, Jan 25, 2017 at 10:27 AM, Shan Mahanama wrote:
> Hi all,
>
> This change has been implemented and available in UUF Core 1.0.0-m11 [1]
> version.
>
> [1]
Hi all,
This change has been implemented and available in UUF Core 1.0.0-m11 [1]
version.
[1] https://github.com/wso2/carbon-uuf/releases/tag/v1.0.0-m11
Thanks,
Shan.
On Mon, Jan 23, 2017 at 12:37 PM, Shan Mahanama wrote:
> Hi all,
>
> We are introducing *onGet*(for GET
Hi all,
We are introducing *onGet*(for GET requests), *onPost*(for POST request)
server side JS functions to the UUF as discussed in the mail thread [1].
Hence the *onRequest* function will be deprecated.
function onGet(env) {
// do stuff for a GET request, env variable is same as before
}