I’ve been toying with the idea of writing a book lately, and this set of hacking instructions for subversion‘s book really got me excited. They describe DocbookLite, the book format used by O’Reilly.
Perhaps some day I’ll write a bit for O’Reilly.
I can think of a few:
- From a webserver, use the Commons FileUpload library and provide a custom class that sends bytes to the EJB instead of the file system.
- From a console program, loop through buffers of the file, and send chunks of the file to the EJB
Does this mean that you have to create a TCP-like idea for your EJB, to
make sure everything got there and is in order?
How well does it handle failures?
What kinds of failures could occur?
Is it really worth it?
Links I’ve found here.
I think it would be really cool to have a set of personal analysis patterns
that I could choose from when creating applications. These could include
solutions I’ve found helpful for:
- Build systems
- Payment tracking
- Email generation
- Project management
They should be searchable, and perhaps include UML designs.