Web Service client, some loose ends

Question

Hi,
I'm working on a portal service which will act as client towards a Web Service outside the portal. Also a Repository Manager will be created that handles the portal service for unification. Environment is NW04 SPS15 + NW Dev. Studio.
The Web Services will expose FILES only, for example MS Office documents.
It’s up to me to specify what SOAP calls the Web Service should support, and how data should be wrapped.
I have a clue on how to manage the big picture, but there are still some loose ends to wrap up:
SOAP call functions:
The idea is to have two methods, one for retrieving a "huge" list of all objects, each object specified with id and all properties, and another for retrieving one specific object by id. The latter would only contain a FileInputStream representing the file and providing the content.
Performance:
Is it advisable to cache the content / input stream as a member variable in the Node object?
Mime Types:
If (for example) one object represents a Microsoft Power Point file, then will it be handled properly by the portal if I provide Mime Type and content? What happens if the file represents an mpeg file? What limitations do I have to consider?
any consideration will be appreciated,
Peter M

Answer 1

You may want to check the response to this previous post to see if it yields any ideas for you:
Not able to Pass header info to Microsoft MapPoint WebService using WLS10