Underscore has spent the last two years developing what we refer to
as the "Sense Framework" for use in enterprise environments. This
framework came about as the result of research into the various
mechanisms and components required to handle event notifications
among disparate applications, including the integration of existing
printer management products.
The trouble appears to revolve around the fact that everytime I try
to describe Sense, I always describe the architecture from the top
down. That is, I describe the components and mechanisms that have
been designed to date, without first adequately describing why we
designed the architecture the way that it is.
What is needed now, IMHO, is a series of discussions that focus on
the architecture from the bottom up, and not from the top down. In
addtition, more focus must be made on how Sense can be used within
embedded environments without the need for an intermediate server,
as commonly described in the current documentation.
Therefore, I will be posting messages to the Sense mailing list in
the very near future that describes the requirements and features for
event messages as it pertains to network printing, without bringing
the existing three-tier architecture into the discussion. This should
result in a bottom-up approach to the problem domain that should
serve to foster an understanding the Sense architecture as currently
defined.
I would kindly ask others in the PWG community to offer their insights
as to how we can advance the Sense effort, or describe similar failings
to date in getting this effort moving.
Thanks for hitting me in the head with a 2-by-4, Dave. ;-)
...jay
----------------------------------------------------------------------
-- JK Martin | Email: jkm@underscore.com --
-- Underscore, Inc. | Voice: (603) 889-7000 --
-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
-- Hudson, NH 03015-4915 | Web: http://www.underscore.com --
----------------------------------------------------------------------