Latest revision as of 15:30, 13 December 2012

When you implement your own TCF processing web service, you have to thinks about the many issues. Is the resource going to be shared among the clients or a separate resource should be instantiated for each client? If the resource is going to be shared, is it thread-safe? If not, how to make it thread-safe? Should my service support processing TCF of any size? If yes, how? The choices you make on those issues depend on the context in which your service is supposed to be used, and on the libraries and resources your service uses under the hood. Each of Creating a WebLicht Web Service tutorials demonstrates one or more of such choices. Below you can find more details on each of the choice with reference to the tutorial that demonstrates a particular choice:

• Instantiation of resources explains when a resource should be created for each client request and when it has to be shared, and how to implement each of the cases;
• Synchronization and thread safety explains about thread-safeness of the resource;
• Response and Request Entity Bodies and Java types explains how Java types are mapped to a HTTP request/response entity body and what Java supports outputting TCF of any size.