Hi Chanaka, Two concerns to clarify..
1) In APIM,we do allow only to upload < 1MB size of thumbnails .Will it be same with new approach..? 3) In APIM, we are storing the API images as registry resources and keep the registry stored image url as an rxt attribute of an API.Thus in this way including the API image and other API meta data are part of registry stored data [in one place].When showing the API in APIStore,we are re-using registry inbuilt governance API to return all API metadata including API thumbnail url and use that registry stored thumbnail url from client side inside <a href> element.This way from implementation level we are re-using registry in built API support and tenancy separation was achieved from registry level..What will be the approach with new storage mechanism..? Thanks; On Tue, Feb 10, 2015 at 8:07 AM, Chanaka Jayasena <[email protected]> wrote: > Hi all, > > I am working on refactoring the Enterprise Store asset specific images > storage logic. Current implementation stores the images in database. But > only MySql and H2 are supported. We have to implement support for other DB > types. Also we have to deal with performance and security aspects as well. > > I am wondering about the option of using registry for the purpose the same > way API Store/Publisher. > > thanks, > Chanaka > > -- > Chanaka Jayasena > Senior Software Engineer; WSO2, Inc.; http://wso2.com/ > email: [email protected]; cell: +94 77 785 5565 > blog: http://chanaka3d.blogspot.com > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Lalaji Sureshika WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +94 71 608 6811 blog: http://lalajisureshika.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
