> that sounds like a lot of import/exports and manual > operations. So there is no plan to have multiuser support > w/o external plugins?
There is currently support for file locking (while saving, to prevent simultaneous writes), detection and merging of external changes, so in principle a small number of people can share a common bib file. I don't know enough about the real-life usability of this since I don't use these features myself (this functionality is always active, but noone else writes to my bib files), and lately I've heard from a user who had problems with the file apparently being locked so one of the users isn't able to save to the file (this looks like a server issue, but I'm not sure). I'd be very happy to hear from users who test this in a realistic scenario. > I guess it should be possible to just replace the internal > in-RAM DB with SQL bindings (i'm a CS master, i have done > this before). It would be ugly and slow, but possible. > > Can somebody with a good overview of the internal data > structures comment on this? This has been discussed before, and I think it is possible. However, I don't have enough knowledge of databases to do this myself. There are some core classes, net.sf.jabref.BibtexDatabase and net.sf.jabref.BibtexEntry and perhaps net.sf.jabref.MetaData, that would need to be changed into interface-implementation pairs, so we could have RAM and database based implementations. I'm sure there will be a number of GUI issues that turn up as a result of these as well, but I think it can be done. -- Morten ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Jabref-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jabref-users
