[cap-talk] YURLs. What is the model of development?
john.carlson3 at sbcglobal.net
Tue Nov 22 01:53:53 EST 2005
Tyler Close wrote:
> Of course, I also wouldn't mind if anyone tried to beat me to the punch.
I think writing this email is getting me closer to doing something,
so bear with me.
I took a quick look at your code. I think I still need the model of
development you are using. Does a Java class file serve particular
web page? How does the XSL and Java interact? How do I follow the thread
of control from a web request through the system? Can you post
a sequence diagram? Should we be focusing on client development
or server side development (I would prefer doing the client side).
How do I determine which parameters your system takes? When
I do a view source, I just get XML. Does the schema attribute
define the attributes the server takes? What are .jos files? I understand
that the user interface is in the XSLT--I will probably use Swing
and ignore the stylesheet. I assume that I will need to seed the
Swing client with the initial YURL retrieved from a web page,
email, or some other means.
You seem to use some syntax coloring. What does what mean?
What is your meta-model? Is there a reason why you don't use
something like XML Schema for your schema definitions?
JSPs are hard to debug. Do your services offer the potential of
better server side debugging, or is most of the debugging now
Overviews are good, but a page that lists the files required
for a particular application and where they go would be good
too. Does the lack of these mean that your server is somewhat
Say I wanted to create revokeable YURLs that would 1) allow people
to send messages to me. 2) Allow me to send messages to the server
3) Allow me access and update my buddy list. 4) Allow others to
post requests to my buddy list. 5) Allow me to copy parts of my
buddy list into a new buddy list. 6) Allow me access to chat rooms
on the server. 7) allow the creation of massive worldwide peer to
peer networks. What do I need to manage all these YURLs,
ignoring the communication aspects.
More information about the cap-talk