Jessie-
Yes, negative states should be considered. What if the
rulet language allowed at a not in the pattern expression,
would that work?
Also, do you have some good examples were a negative expression
is key to making it work?
Michael
To: <condry(_at_)condry(_dot_)org>
Subject: Re: EPSFW Workshop Followup
Mime-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by jurassic.eng.sun.com
id
e8JAN2a895281
Just to comment, in addition to the rules listed in UAUseCase.txt, it may be
a
good idea to provide a reverse set of rules:
i. Fire (or do not fire) for all URLs
ii. Fire (or do not fire) with URLS matching a regular expression
(like
"149.146.22.*")
ii. Fire (or do not fire) with URLs found in a list
This provides the customer with the flexibility to manage by exception.
Cheers
Jesse
***
Jesse Pretorius
Systems Engineer
e-mail: JPretorius(_at_)Novell(_dot_)Com
AIM/InstantMe: preycor
ICQ# 4620796
Tel: +27 21 418 3805
Fax: +27 21 418 3931
Novell, Inc., the leading provider of Net services software
www.novell.com
"Michael W. Condry" <condry(_at_)condry(_dot_)org> 09/18/00 06:20AM >>>
After our EPSFW workshop I have some notes on some of the work
that might be done between now and San Diego. We wish to
expand the specifications associated with our model and enhance the
requirements to evolve the EPSFW draft. The details will be in
clarification
of how things could work, needed protocols, APIs, etc. all of which will
define pieces that eventually evolve the overall architecture.
I will be posting the slides and notes later.
Let me try and spell out some things to do, and I would like some
volenteers
and additions. Please make suggestions!!!
1. Services/Proxylet requirements:
Here a particular service is examined in detail, with a
use case or implementation or both. Results will exhibit the
specifications either at the detailed level (APIs and protocols)
or at the requirements level.
Alex Shah gave us a detailed Use Case for his
MyWebBook. Markus Hoffman and Katy Guo gave us some
implementations that could be mapped into the
framework. Senthil Kumar
<Vs(_dot_)Senthilkumar(_at_)india(_dot_)sun(_dot_)com> and I tried to
enhance the "University Accounting" USE-CASE.
Things we need to do (as much as possible)
a. Explain what needs to be done including examples of required
protocols, functions, rule expectations and library
expectations.
b. Propose a design that is consistent with the requirements in EPSFW.
Suggest requirement changes if necessary.
c. Implement code for the service or show how thing need to work
with a detailed Use Case.
d. Describe enhancements or details to the EPSFW framework.
Senthil Kumar <Vs(_dot_)Senthilkumar(_at_)india(_dot_)sun(_dot_)com> and I
tried to
enhance the "University Accounting" USE-CASE. Kumar's
group may be able to implement this by San Diego. This is
quite simple and no example protocols or APIs are shown
thus far.
Example Service Projects that I can think of:
* Steaming Media with Caching changes
* Content Assembly - improving Yahoo
a. Ad insertion
b. Tickertape
c. MyWebBook
d. Localization
* PBX control
* Transcoding
* University Accounting
* ICAP examples
Look the list over, pick one or insert more in the list.
2. Rule Model
Dave Farber started with some rule issues and Markus has sent
out some additional requirements. We need to collect
these requirements and update the draft.
We could also build a small rule engine. Just a simple case could
be used to expand things:
* HTTP/HTML only - certainly not the framework requirements.
* Schema to represent rules
* Simple conflict model
Now we need
* tools to analyze rule specifications
* engine for executing rules and firing proxylets
lots more.
3. Security/Accounting
What is the AAA model for our EPSFW environement.
Understanding the scope of rulets and proxylets
is critical. There is lots to be done here.
I am certainly open to suggestions.
Michael
condry(_at_)condry(_dot_)org