Hi,

I am working on a utility API. Basically, this would be an application/web-app with a 
servlet/class that will load some data from various property/text files into 
Hashtables (or classes extending HT), cache it using OSCache for, say 1 week, and 
service client requests. 
Another application (which can be any web-application, the Utlity API shouldn't bother 
about it), lets call it client application, has a servlet that will send request to 
this API (say request for translating a word to another language). The API will search 
for the translation in the Hashtables and return it to the servlet if found (or an 
empty string if not found). 

I am really not able to imagine the design part of it. My API should have abstraction 
so that any client API can use it. The API on the other hand should be something like 
a service (apart from usual java classes) that updates the data after the OSCache TTL 
expires automatically.  Actually I am envisaging a Servlet in the utility API because 
I need some sort of service that automatically reads the data from property/text files 
periodically (as per the TTL of OSCache) and has the Hashtables loaded in memory, 
ready to respond to the client Servlet. 

I could have kept the hash data in a database but I want to avoid that. The data is 
not changing too frequently and is hence cached and updated only in say a week or so. 
The client Servlets would be given responses based on this cached data.

Is the Avalon framework suitable for this server-side Utility API, if no can any other 
framework of jakarta project help?

Thanks,

Debashish Chakrabarty



Reply via email to