I am on manufacturing field and I am about to integrated the QR codes as a part of the production system for tracking the URL to the document in the data base that keep information about the product with 2D-barcode scanners. There is API for generating uuid-s and I thought would be nice to have some of the url features as utility APIs integrated. But actually you are right it is application logic and could be easily implemented as a show function in a couchapp.
Begin forwarded message: > Date: 26. Januar 2011 23:31:04 MEZ > Subject: Re: native support for url-shorteners and qr codes? > Source: [email protected] Archives > Author: Keith Gable > > On Wed, Jan 26, 2011 at 3:46 PM, Benoit Chesneau <[email protected]> wrote: > > On Wed, Jan 26, 2011 at 10:00 PM, Nikolai Teofilov <[email protected]> wrote: > >> I'm just curious why not ship couchdb with native support for url > >> shorteners and > qr codes. This might be very helpful. > > > > why native support ? > > > > +1. > > My 2 cents follow: > > CouchDB is a database... You wouldn't SELECT QR_CODE() FROM users > WHERE id = '1234' or SELECT BITLY_URL('appid', 'secret') FROM articles > WHERE id = '1234'. > > Also, assume that CouchDB is able to figure out the self-referential > URL for an object. Is that what you want in the QR code? If the > document describes a person, wouldn't you want the QR code to have > their contact info in it? Or if you're in manufacturing and the > document describes a product, wouldn't you want the QR code to have > tracking information, like what machine made it, when, and so on? > > It's application logic - put it in the application layer.. which > could, in the case of a CouchApp, also be in JavaScript, but it could > just as easily be your Ruby app or your shell script... > > -- > Keith Gable > A+ Certified Professional > Network+ Certified Professional > Web Developer > > > Read more… >
