David Freeman david_freeman@rocketmail.com writes:
David, trim your quotes, please. ;-)
Centralisation. As much as I like the idea of the Peer-to-peer networking technique it, like most ideas, is only applicable to certain tasks, and I believe this isn't one of those. I think a hybrid of peer-to-peer and centrailised systems much like napster would be a good solutions.
Well, this has been covered in the earlier messages, but unless we have this p2p scheme, then either books will have to only change hands at our irregularly-spaced meetings when the borrowers are both present or whoever is the librarian will have to travel a lot.
I may also model the relational scheme or I may do it as objects to be written in java.
Oi! Implementation issues! Make your mind up! ;^)
[...]
"yes, Joh do you have the book I gave you at the last meet?" "No I wasn't at the last meet" "So who got that book then?"
This is why the ticket-code system was being mooted.
As I understand it, it could work like this: the prospective borrower gets a release code on their request which is also sent to the current borrower. The current borrower checks that the person asking for the book has this release code when handing the book over, then confirms the handover to the library system, once again with the code.
I will have to confiscate your fine adjustment tool at the next meet. Every engineer knows that a large ajustable spanner works better, after all it has more uses than just bugdening something :o)
Adjustable spanners are crap. They break when you bludgeon things with them.
oh goody an interative development process.
Is this sarcasm or not? :-S