Currently writing code for URLyBird.
A hotelroom booking agent that
- A. requires a new rmi-based server ( server: concurrent! but should also be capable of running in non networked mode) that uses a database with an interface that MUST follow and reads from a custom databasefileformat.
- B. requires a swing client to let the phonemonkeys (multiple: concurrent!) book hotel rooms on certain day without booking the same room at the same time (recordlocking) or booking twice
Sounds simple this way. But it’s a lot of work. Encountering problems with things I’ve never used before. A learning path, yes it is.
Do remind myself to multiply estimated development time by 2.5 next time…
But URLyBird let us swear an ode not to leak any implementation details so I can’t tell more.