We have an internally available domino based intranet and an externally available Portal based website.
We are currently using WPF/WDF to display data from our domino servers to external customers which all works fine.
Now a requirement has come up to allow them to access attachments within a Notes Database.
I was planning to use the Domino Attachment builder, but it seems that (and I didn't notice any documentation warning me of this) that whereas most domino builders for WPF allow users to communicate to the WAS server which then makes separate backend calls to the domino server over DIIOP, the links generated by the Attachment builder point directly at the domino server. This won't work for us as the domino servers aren't externally available and even if they were we have a different authorization model for domino and WPF.
Am I missing something - is there no builder that allows you to serve up attachments from domino with the user only communicating directly with the WAS/Portal server?
Pinned topic Domino Attachment Links point directly to the Domino Server
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-07-13T17:55:42Z at 2009-07-13T17:55:42Z by SystemAdmin
SystemAdmin 110000D4XK334 Posts
Re: Domino Attachment Links point directly to the Domino Server2009-07-13T17:55:42ZThis is the accepted answer. This is the accepted answer.Correct - by design and for best performance, attachments are served up directly by Domino's web server. However, you could code this functionality.
For flexibility, the Domnio builders expose the lotus.domino.Session and lotus.domino.Database objects from the Domino Java API. This is described in the Domino builder help. So you could code to the Domino Java API to achieve the functionality you desire, although it might not perform well.
For example, an action could call a Method builder of LJO builder which contains code that would use the Domino Java api to retrieve the current document, save the attachment off to the file system temporarily (be sure to give a unique name!), then serve up a link to the temp file. Again, performance might be a concern since you've added a hop.