The project I want to use Avalon for is a server so I'm considering getting started with Phoenix (based on the recent Wiki info). Right now it's a background deal which explains my lack of time to work on Avalon too much.
Joe,
I was where you are about a year ago. Considering Avalon for a server project, and I went with Phoenix mainly because Merlin was still under heavy development.
However, Merlin is now mature and provides you with nearly everything that Phoenix does, plus much more stuff that Phoenix cannot do. My recommendation is to just start with Merlin. The documentation, tutorials, examples, and support far exceed what you'll find on the Phoenix front.
I'm currently developing a new server application using Merlin, and beginning to plan to migrate last year's Phoenix application to Merlin.
Regardless of the banter you might see back and forth about containers, be advised of one thing. Avalon technology (across all containers) is solid, reliable, and makes sense. Our Phoenix application is running in a commercial environment.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
