Hi there,
I am a HUGE SQLite fan and have an interesting question I have been scratching my head about for a couple days now. First off my daily job is very much around "messaging" and I am very familiar with message queue products like Websphere MQ and Fiorano MQ. When you install Websphere MQ or Fiorano MQ they have a FILE based queue underneath by default (typically one file per queue with the messages etc stored at different offsets). There messaging systems will have "file writer locks" that in essence will only allow ONE WRITER per queue at any one time. So any clients sending messages will have "to wait in line" until the message can be physically written to file. Bottomline: We have one writer and multiple readers per queue....fine. Then I scratch my head and wonder why SQLite is not the PERFECT persistence layer for building an awesome "file based queue" on? It is lightening fast by default, and also has the same "locking issues" described above. We are talking milliseconds anyway....between writes.... Bottomline: Is there any reason why anyone would think someone like me coding a solid message queue using SQLite is a bad idea? Am I missing something? I personally think it is a wonderful idea and would be hugely useful to my daily job.... Any help or advise in this regard would be hugely appreciated ;-) Thanks Lynton _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
