Random logic is always an alternative. Without having the slighest idea
what you are trying to do, I would point out that a generalized state
machine itself could be written in very little code. The trick is
to specify the state transition rules. If you write a (small)
application-specific compiler and implement a table driven 
state machine, it should be small, fast, and maintainable.
There can be a start-up time issue if you need to load a large
state transition table. 

What is it that is Servlet specific that is impacting 
your architecture? Are you contemplating subclassing
issues and don't want a long processing chain
( super.doPost() ad infinitum ) ?


Mike Marchywka
Senior Engineer
EyeWonder
2859 Paces Ferry Road
Suite 1200
Atlanta GA 30339
770-261-5084(W)
770-434-7510(H)
FAX: 770-261-5080
[EMAIL PROTECTED]
 

-----Original Message-----
From: Stuart Hemmings [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 12:15 PM
To: [EMAIL PROTECTED]
Subject: StateMachine vs Extensible Servlet


Does anyone have a viable alternative to implementing a 'state machine'
in a
Java Servlet. The reasons for the request is to find a suitable method
by
which the size of the doGet and doPost methods will reach as new code is
added to the Servlet and it permits new storyboards (States/actions) to
be
added.

     Stuart Hemmings
     Imagine Broadband Limited

p    Golden Cross House, 8 Duncannon Street, London, WC2N 4JF, United
Kingdom
t    +44 (0) 2 07 831 7890
f    +44 (0) 2 07 484 5136
m   +44 (0) 7803 034 777
e    [EMAIL PROTECTED]
w   www.imaginebroadband.com
This e-mail and any attachments are confidential and may also be
privileged.
If you are not the intended recipient (or have received this e-mail in
error) please  notify the sender immediately and destroy this e-mail.
Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

________________________________________________________________________
___
To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to