Tony, >Paul, > >Maybe I should clarify a few points. The echo server that I am talking about is just >a simple example that I was hoping could easily demonstrate some very basic Avalon >functionality. It will listen on some configurable socket for some request and echo >it back to the client. That was really all I intended. Maybe it is too basic but >the idea was to demonstrate Avalon not implement some huge server. They are intended >as examples only and my intention is to make something that the Avalon team would >deem fit to include as examples. > Understand. I thought you meant the RFC specified 'echo'.
>You were right. I was not talking about Phoenix. Unless I am mistaken, Phoenix >seems to be several steps beyond where I was planning to start. It would be a good >idea to evolve it to a Phoenix example but, when you reach that level of >sophistication, the example may be too simple. > Well then < devils advocate mode = on > Avalon Framework and Avalon Excalibur are not necessarily just for servers. They are equally applicable to client side code. >I looked at the examples and they still jump in much deeper than I wanted to start >with. I am getting the impression that maybe there is not a need to start as basic >as I am proposing (?????). I wanted to start just by demonstrating the concept of >COP (as simple as it can be). Too basic for most and probably not a very practical >application but, an example none the less. Am I the only one that feels there is a >need for this? > I had kind thought that the PDK showed the simplest of all servers that used Avalon concepts. Next to that, I had thought that the HelloWorld demo was also quite simple.... I guess my education will continue upon seeing the product of your labors. We will of course integrate simple demos to the codebase if suitably attributed as Apache license... Regards, - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
