On Wed, Nov 2, 2016 at 7:23 AM, Ayyoob Hamza <[email protected]> wrote:
> different
I am with Ayyoob in that the term "feature" sounds very much something from
the mobile world. But if you think about it, any functionality that a user
sees on the dashboard of a device type is a feature. So I am +1 for
bringing feature definition down to the mobile plugin in form like.
<Features>
<Feature code="abc">
<Name>abc</Name>
<affectedVersion>5.0.0</affectedVersion>
<Description>this is a feature</Description>
<FeatureProperties>
<Property name="prop1">place_holder</Property>
<Property name="prop2">place_holder</Property>
<Property name="prop3">place_holder</Property>
</FeatureProperties>
</Feature>
</Features>
But somewhere down the line when it comes to orchestrating device
integration flows, we most definitely as Ayyoob mentioned, have to
take a look at Vorto... which is very cool IMO.
Thanks and Regards,
Ruwan Yatawara
Associate Technical Lead,
WSO2 Inc.
email : [email protected]
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
https://500px.com/ruwan_ace
www: :http://wso2.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
