Resending. Bounced back. On Wed, Mar 9, 2016 at 2:28 PM, Sumedha Rubasinghe <[email protected]> wrote:
> But this a programmer that we are talking about. > > It's contract first vs code first IMO. > Our current approach is more close to code first now (and its not that bad > IMO). > > > > On Wed, Mar 9, 2016 at 2:09 PM, Ruwan Yatawara <[email protected]> wrote: > >> Hi All, >> >> Had a chat with Joe, to gain some feedback on his experience of using the >> IoTServer to declare his custom device type. >> >> One complaint that came up was that the hardware vendor needs to navigate >> to the controller and manager interfaces and declare the structure and >> outputs of the APIs, in code. We could very well automate this by giving >> users the option to draft the structure of the API and output via a >> definition language like swagger. Based on these inputs we may go ahead and >> declare the stubs that can be later filled in by the user. >> >> This would make life easier for the vendor, and will also be invaluable >> IMHO in our tolling strategy when we integrate the archtype to DevStudio. >> >> Thanks and Regards, >> >> Ruwan Yatawara >> >> Senior Software Engineer, >> WSO2 Inc. >> >> email : [email protected] >> mobile : +94 77 9110413 >> blog : http://ruwansrants.blogspot.com/ >> www: :http://wso2.com >> >> > > > -- > /sumedha > m: +94 773017743 > b : bit.ly/sumedha > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
