Thursday, October 29, 2009

Frisky is merging into magnum

I created a web server to experiment with some concepts about a WSGI web server. The other day read about magnum which is the exact same concepts but with a much cleaner implementations. I was planning on spending the holiday rewriting Frisky to something usable. It is nice to know that there are some like minded people out there. I will now be taking the features that I experimented and ended up being good and rewrite them and submit my patches to magnum.
Once I can get my existing software working on magnum I will sunset Frisky. Based on the conversations I have had on the magnum mailing list magnum will be faster and better implementation of the same concepts soon enough. The collaboration will do me good I am happy to get out of my cabin in the woods.
Posted by at 8:19 AM
Labels: , ,

3 comments:

  1. What frisky features are you are looking to add to magnum?.

    Have you had a chance to take magnum for a spin?

    I am curios to see how well magnum performs.

    Brume
    ReplyDelete
  2. First I have to port Magnum to OS X. Which I have started to write a generic nonblocking I/O system that uses kqueue, epoll or poll depending on what is supported (probably support libevent pretty easy to). I have the code stubbed out but I need to finish testing and implementing it. I have a little Android app I am writing this week, then a little web app and hopeful I will find a small consulting project and then I can go back and finish the implementation. Once I get the port it shouldn't take more than 2 days to port all the features Frisky has into Magnum. Would love some help on the implementation if anyone can?
    ReplyDelete
  3. I would gladly help out if I can. Not sure if I will be in a position to help but I will contact you shortly.

    Regards,

    Brume
    ReplyDelete

Subscribe to: Post Comments (Atom)