Dear All, We've just started writing some CardServices encapsulating operations that can take a long time to complete, such as loading a card application. To make sure the user is informed that something is going on, and to give an idea of time remaining etc we've used the event listener pattern. The application registers with the CardService and is notified when progress has been made so any gui can be updated. The granularity of these events is the responsibility of the CardService - an event could be generated with each APDU, or only at significant milestones such as file created etc. My question is this. In view that a lot of operations are of this nature, i.e. multiple operations taking some time, is there any merit in adding support for this in the base-opt, or possibly another, package ? Although the OpenCardEvent class exists at the moment, there is no class for managing & notifying the event listeners. Strategies for such class implementation are well known (see http://www.javaworld.com/jw-09-1998/jw-09-techniques.html for a good overview) but re-implementing again & again is a waste of time. I for one would find inclusion of such support in OpenCard most useful. Jon. Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for access to documentation, code, presentations, and OCF announcements. ----------------------------------------------------------------------------- To unsubscribe from the OCF Mailing list, send a mail to "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the message.
