Hi Nuwan, One other approach suggested to me was to use a *Siddhi Stream for both > storage and retrieval* purposes. This would further allow for analytics > to be performed on the data which not be very much possible with the > earlier mentioned approaches.
Have you evaluated this approach? What are the advantages and drawbacks in terms of storage and retrieval of images by following this approach? On Tue, Jan 16, 2018 at 12:36 PM, Geeth Munasinghe <[email protected]> wrote: > > > On Tue, Jan 16, 2018 at 10:52 AM, Nuwan Jayawardene <[email protected]> > wrote: > >> Hi all, >> >> I'm currently working on a project to add image storing and retrieval >> capabilities to the WSO2 IoT Server. >> >> To achieve this I have implemented the following; >> 1) Added a separate DAO Table with a field with LONGBLOB data type for >> storing. >> 2) Added storage capabilities in the database for an image sent as a *File >> *in the form of a *BinaryStream*. >> >> As of now, I've written unit tests and the test images are getting stored >> successfully in the database. >> >> The problem lies in how to successfully retrieve the stored data. For >> this, I have come across 2 possible approaches. >> 1) *Retrieve as a File - *The notable downside I realized with this >> solution is that each time a new Image is retrieved, a new file will be >> created. Therefore measures would have to be taken to persist new files >> while purging older obsolete ones. >> 2) *Retrieve as BinaryStream - *Although this requires no persistent >> memory usage and the data will only be retrieved on call and issues may >> come up when representing that data from a UI end. Further analysis is >> required for this approach. >> > > +1 for retrieving as a BinaryStream. This will make it easy to handle in > the java level unlike handling as a file. This has to work in the cluster > of servers, hence retrieving as a file will cause other syncing issues. > > >> 3) *Retrieve as FileOutputStream - *This is my preferred method and the >> one recommended mostly in forums and tutorials. >> >> One other approach suggested to me was to use a *Siddhi Stream for both >> storage and retrieval* purposes. This would further allow for analytics >> to be performed on the data which not be very much possible with the >> earlier mentioned approaches. >> >> Suggestions and Feedback are appreciated. >> Thanks and regards! >> >> -- >> *Nuwan Jayawardene* >> *Software Engineering Intern* >> *WSO2, Inc.:http://wso2.com <http://wso2.com/>* >> *lean.enterprise.middleware* >> *Mobile :- +94 71 1813299 <+94%2071%20181%203299>* >> >> >> - *Linkedin* *:- **https://www.linkedin.com/in/nuwa >> <https://www.linkedin.com/in/nuwanjaya/>**njaya/ >> <https://www.linkedin.com/in/nuwanjaya/>* >> - * <https://www.wso2.com/signature>* >> >> > > > -- > *Geeth Munasinghe* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: [email protected] > phone:(+94) 777911226 <+94%2077%20791%201226> > > <http://wso2.com/signature> > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 IoT Team Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. > -- Madawa Soysa / Software Engineer [email protected] / +94714616050 <+94%2071%20461%206050> *WSO2 Inc.* lean.enterprise.middleware <https://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
