Hi Sanjiva, Udara and all, If we are using PHP API we have to workout Authentication/Authorization for Registry Rest API because it is not possible to access it straightaway - could be OAuth. My other concern is the nativeness of the approach. Would developers feel it is a natural way?
As Udara suggested if there is a Metadata service in Stratos, we can be using it. It would yield a more natural way to developers. Isn't it? It was Paul who suggested the file-system (or environment variable) approach, sometime back. thanks, dimuthu On Sat, Nov 8, 2014 at 11:05 PM, Sanjiva Weerawarana <[email protected]> wrote: > Dimuthu I don't understand .. why can't you continue to use the registry > for these and just give a local API for PHP or whatever to get it from? We > can simply have an agent in the cartridge that fronts the registry and then > gives a local HTTP endpoint to get the data as name/value pairs. > > IIRC Paul suggested this many years ago. > > Sanjiva. > > On Sat, Nov 8, 2014 at 10:48 PM, Dimuthu Leelarathne <[email protected]> > wrote: > >> Hi Udara, >> >> Is it available in the new version of Stratos? >> >> So when we write to Metadata service, how is my app suppose to get it? Is >> it via environment variables? >> >> thanks, >> dimuthu >> >> On Sat, Nov 8, 2014 at 10:45 PM, Udara Liyanage <[email protected]> wrote: >> >>> Hi Dimutu, >>> >>> How about using a metadata service for this. Metadata service is a REST >>> service where its provides APIs to publish and fetch key value/values pairs. >>> This is already implemented in Stratos. >>> >>> So workflow is, >>> Instead of writing to git, AF publishes to metadata service. Then >>> cartridge agent fetches from the metadata service and expose as env >>> variable. >>> I feel this is more cleaner than commiting to repo. >>> >>> >>> >>> >>> >>> >>> Touched, not typed. Erroneous words are a feature, not a typo. >>> On Nov 8, 2014 10:33 PM, "Dimuthu Leelarathne" <[email protected]> >>> wrote: >>> >>>> >>>> Hi all, >>>> >>>> For propagating resources (name-value pairs for Apps) to none-carbon >>>> runtimes we need an approach. I have been thinking about the possibilities >>>> and this came into my mind. >>>> >>>> https://creately.com/diagram/i296mkhn1/kguXC7mpUdJsUELKTcjbNrrT4%3D >>>> >>>> WDYT? Are there different suggestions? Or improvements? >>>> >>>> thanks, >>>> dimuthu >>>> >>>> -- >>>> Dimuthu Leelarathne >>>> Architect & Product Lead of App Factory >>>> >>>> WSO2, Inc. (http://wso2.com) >>>> email: [email protected] >>>> Mobile : 0773661935 >>>> >>>> Lean . Enterprise . Middleware >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; office: (+1 650 745 4499 | +94 11 214 5345) > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: [email protected] Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
