>>> 7. I think a really cool example would be to have a >>> simple application written in non-avalon way and then >>> show users how to convert that into Avalon form and >>> explain the benefits.
>> If you have such a "non-Avalon" app available, I think I >> and Aaron could take a shot at it. (And don't send us JBoss >> or similar :o) ) > Sounds like a fine idea. > I was starting to do something similar with my 'mutuals' example. > And I think Timothy's webserver example is a good candidate > for this sort of thing. I would like to see the very simple example that Sun put together to demonstrate threads and sockets done in this manner as an example. This example is part of the official Java "All About Sockets" tutorial. I like their approach, which is to take an example that all can understand and build upon it (or in this case, make it work in avalon/merlin). If you take a more difficult example, then the program details may get in the way of people understanding what the framework is doing, so lets keep it VERY simple. In this case, I could see it done as maybe 2 containers, one for the main logic, listening for sockets, and one to handle the new threads ? The url to their example (took me like 5 minutes to get their code downloaded and working) is located at: http://java.sun.com/docs/books/tutorial/networking/sockets/clientServer.html the client part is in the same tutorial if needed, it is: http://java.sun.com/docs/books/tutorial/networking/sockets/readingWriting.html If we could domonstrate a merlinized bversion of this tutorial, we could show how sockets, threads, logging, etc are handled, in an easy to understand app. One note to add... im wondering if copyright issue could be a problem. If so, I volunteer to write my own version of this tutorial that just responds with hello-world stuff instead of knock knock jokes, so we won't get in trouble. Then if someone could help convert it into a usable container setup we would be good to go. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
