Hi Chan,
> I believe - we first thought of implementing a sort of Storage App that > would perform this. Registry is used to store Meta-data -not Date by > itself. IMO -storing binary data would become a performance bottleneck for > the registry. I believe - we need to build a service (JAX-RS perhaps) that > handles these aspects. The service can further expand to storing it on a > database, storing it on disk or storing it on S3. > Yeap, this was the original plan but we do not yet have such a mechanism in place.This proposal was to utilize the registry for the immediate release (1.2.0). Thank You, Sameera On Wed, Aug 13, 2014 at 8:33 AM, Udara Rathnayake <[email protected]> wrote: > Hi Dakshika, > > > On Wed, Aug 13, 2014 at 5:52 AM, Dakshika Jayathilaka <[email protected]> > wrote: > >> Hi, >> >> IMO we need mechanism to store assets on external locations as wel. (ex: >> dropbox, fileshare ) >> most of the time users do not want to waste their bandwidth on >> downloadable stuff. but in this case we need to implement verification >> mechanism as wel. (SHA or MD5 hash for linked files) >> > > If those resources are publicly available in any third-party service, you > can simply have compatible rxt definition and give that public downloadable > URL to access. I don't think we should support authentication mechanism for > third-party service OOTB since anyone can implement that as an extension > within ES using APIs provided by those service providers. > > In order to check the integrity again we can have an extension according > to the APIs provided by service provider. So I still believe this is a more > specific use-case. > >> >> WDYT? >> >> Regards, >> >> *Dakshika Jayathilaka* >> Software Engineer >> WSO2, Inc. >> lean.enterprise.middleware >> 0771100911 >> >> >> On Tue, Aug 12, 2014 at 5:53 PM, Sameera Medagammaddegedara < >> [email protected]> wrote: >> >>> Hi Everyone, >>> >>> *Current State:* >>> >>> - All the resources of an asset are stored in a database(e.g. images >>> and pdfs) >>> - The embedded H2 database is used as the default data source >>> - CRUD operations are performed using an intermediate layer that >>> abstracts out the complexities of dealing with different database types >>> - The business logic deals with an interface that uses get and >>> put methods to access the storage layer >>> - All resources are served from a single endpoint that is used to >>> control access based on the state of the asset that owns the resource >>> >>> *Problems with the current implementation* >>> >>> - The need to test and support the storage implementation across >>> databases other than H2 and MYSQL >>> - The need to replicate tenancy within the database schema >>> - The need to enforce access control logic in the endpoint used to >>> serve the resources >>> >>> *Proposed Solution* >>> >>> - Store and serve the resources using the registry >>> - *Advantages:* >>> - There will not be any need to support multiple database types >>> at the ES level >>> - The use of registry roles to control access to the resources >>> - *Open Questions:* >>> - Is it prudent to serve content from the registry? >>> >>> >>> Thank You, >>> Sameera >>> -- >>> Sameera Medagammaddegedara >>> Software Engineer >>> >>> Contact: >>> Email: [email protected] >>> Mobile: + 94 077 255 3005 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > *Udara Rathnayake* > Software Engineer > WSO2 Inc. : http://wso2.com > > Mobile : +94 772207239 > Twitter : http://twitter.com/udarakr > Blog : http://udarakr.blogspot.com > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sameera Medagammaddegedara Software Engineer Contact: Email: [email protected] Mobile: + 94 077 255 3005
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
