[SERVER-9789] REST interface for querying properties content Created: 28/May/13  Updated: 01/Aug/15  Resolved: 01/Aug/15

Status: Closed
Project: Core Server
Component/s: HTTP Console
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Julien Alric Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12730 Full HTTP Rest interface Closed
Participants:

 Description   

I propose here an elegant way to transform mongodb in media server.

Currently, in most cases, we have a media server and a database containing metadata about this medias. Something like that :

{
"_id" : "image_id",
"url" : "http://media.domain.com/image.jpg",
"tags" : ["tag_1", "tag_2", "tag_3"],
"description" : "lorem ipsum..."
}

We use this datas to retrieve the image url and insert it into the html document. Like that :

<img src="http://media.domain.com/image.jpg">

The problem? Data and metadata are separated. Why not have something like this :

{
"_id" : "image_id",
"image" :

{ "jpg" : "binary datas of the image" }

,
"tags" : ["tag_1", "tag_2", "tag_3"],
"description" : "lorem ipsum..."
}

And the ability to retrieve content like this (mongod on port 80):
"http://server/database/collection/id/property"

Then we will be able to do :
<img src="http://media.domain.com/database/collection/id/image.jpg">

We can of course consider using a proxy (in Java or Php for example) between the client and the binary datas in mongo, but it would be too slow in terms of performance.

In the real world the problem is a little more complex. The mongo server should be able to return the mime type for the image format. But beyond that, I find this feature very elegant and mongodb would no longer only a database server, but also a media server (for small media such as images).



 Comments   
Comment by Ramon Fernandez Marina [ 01/Aug/15 ]

jalric, I'm going to mark this ticket as a duplicate of SERVER-12730, since that ticket is really a superset of this one.

If we determine that the functionality requested here can be implemented separately from SERVER-12730 we can always re-open this ticket and schedule it separately.

Regards,
Ramón.

Generated at Thu Feb 08 03:21:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.