Slashdot Mirror

← Back to Domains

Domain: conman.org

Stories and comments across the archive that link to conman.org.

Comments · 8

  1. Useful book by Anonymous Coward · · Score: 2, Informative · on HTTP: The Definitive Guide

    I used this book in addition to the RFC when writing my webserver software.

    It's a good addition to the RFC's but not a substitute. The introductory stuff is a bit too basic but the rest of the chapters clarify several things about the RFC's. 2616 can be a bit ambiguous at times.

    All in all, it was worth the money if you are planning to do any serious work with HTTP.

  2. I wonder... by Anonymous Coward · · Score: 0 · on Dreamcast Web Server Running Off Memory Card

    I wonder how my
    embedded webserver would handle the load on a dreamcast.

  3. Relays? by Anonymous Coward · · Score: 0 · on Building Your Own Glowing Cyber-Balls?

    You don't want relays, you want a DAC and a CPU. The combination I can recommend is an AVR 8-bit micro controller and a Maxim 4-channel quad DAC with an SPI interface.

    This is a very simple combination to program as well as design the hardware around. You take your micro controller (whatever your preference is -- hopefully it has an SPI bus) and you tie one GPIO lead to the chip select of the DAC.

    Have three of the DAC outputs drive MOSFET amps and then the LED's. You can then take the serial port of the micro and hook that up to a convenient PC.

    You can then devise a simple command structure to tell the micro to do various things (freeze a color, color wash, random, etc).

    The SPI bus is a nice little addressable serial bus (a bit like I2C), its easy to connect electrically and simple to program.

    Add some bulking caps and a a pull-down (I think its down) to the CS line of the DAC (when the AVR initializes the line will be high-z).

    Or you could get a more impressive microprocessor and port my embedded webserver to it (I just love plugging it)

  4. Hardware Longevity by Anonymous Coward · · Score: 0 · on Technologies that Have Exceeded Their Expectations?
    I'm still amazed at how long my webserver has lasted. It's a 16MHz 486SX. The hardware has been running without failure for years.

    I can't even think of the last time I saw it at its colocation facility. I wish newer hardware lasted so long.

  5. Seminole by Anonymous Coward · · Score: 1, Interesting · on An Overview of the Boa Web Server
    As a total shameless plug, you can also check out a webserver I wrote designed specifically for embedded systems: http://www.conman.org/software/seminole/

    Enjoy.

  6. Re:common factor by Anonymous Coward · · Score: 0 · on Sites Rejecting Apache 2?
    As the developer of another multi-threaded webserver, I can tell you that threads aren't so great under BSD, at least Open and Net (I have never looked at FreeBSD).

    But threads in those systems are basically user-land and tend to not take advantage of things as much as real kernel-level threads can.

    So I'm not so sure that Apache 2.0 will gain all that much popularity except on systems like Solaris, AIX, and WinNT where the kernel implements real threads with a real saving in context-swith and I/O overlap time.

  7. Open Source alternative by Anonymous Coward · · Score: 0 · on Controlling An Embedded Device Using Flash
    You could always use my open source webserver, Seminole, which is designed for embedded devices.

    Doing XML-RPC is nothing special for a webserver.

  8. Re:I support PG, but... by spconner · · Score: 1 · on Giving Project Gutenberg Recognition
    While they may not look great as plain ASCII, as long as they're consistant in formatting with ASCII it's relatively easy to break up and reformat for the web.

    Last week I downloaded a version of the King James Bible (bible10.txt---almost a 5M textfile) and because of the consistant formatting, was able to break it up into book, chapter and verse and create an online version that was primarily (for me) an experiment on making a web-friendly version of a hiarchially structured document (Book.chapter:verse etc).

    More, or inconsistent formatting, would have made the job more difficult that it was.

    -spc (Converting the text was the easy part ... )