Guys, Gurus,
In my current project, we are thinking to provide our functionality in a form of webservice, rather than a jar file. So people are talking about using DFS.
I read the developer guide, built and run sample project, with/without PL, everything works fine. And then this question hit me, should I use DFS?
In my project, we need provide a way for customer outside of company upload content files into DCTM repository inside firewall. Because the nature of this request, I am thinking create a standalone repository just for uploading file purpose.
At first I feel that even though back end is DCTM repository, my service should better be flexible to allow me swap different implementation later on. So the wsdl should be product neutral. Anything change on my side, my customer won't get affected.
Then I am thinking, i can create a POJO class, contains all the server side logic. For this server side logic, it need access DCTM repository. I could use DFC or DFS.
DFC is quite straight forward, I can code anyway I want. But, DFS? I dont see the value DFS brings here. The out-of-box DFS is very granulized. The only benefit I can see here is, using DFS allow me bypass restriction on firewall. I can use HTTP. But calling DFS comes with its own overhead. If I use local customer, then why not write DFC directly.
Another problem with DFS (correct me I am wrong) is that, serverside DFC session is kept open after service invocation. There is no easy way to disconnect/release this session. But this will not be a problem if I write DFC.
So, think over this requirement again, I feel there is no place for DFS. I dont know, maybe my starting point is wrong.
Thanks for reading this. And more appreciated if you can share some of your thought on DFS.
-beef
