Github user lazedo commented on the pull request:

    https://github.com/apache/couchdb-fabric/pull/33#issuecomment-179789279
  
    @kxepal maybe i'm missing the objective of this feature. as i see it, a 
external attachment would still create the stub information about how to reach 
the `real` attachment. the `stub`would have the information needed to get the 
attachment back, so, you would need to store the `driver` in case the 
configuration is changed and you start using another driver but still want to 
reach the already stored attachments. the `options` would allow more 
flexibility to the driver creating the necessary stub information needed to get 
the attachment back and also to choose which driver we want for the attachment.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to