[jsword-devel] Storing user information in JSword

[Chris Burrell]

Indeed, I have seen, and we should change that.  Did you have any insight in
terms of the defect I raised? I'm happy to create a patch for it, but I'm
not very familiar with that part of the code, having used mainly the exposed
API. And so, it would be good to get feel for the way to go about the
change, before I change one of the most crucial parts of the whole library!
And also whether the other drivers would suffer from the same problem.

You probably know this already, but a few good principles I've picked up
over the last few years:
- dependency injection is good and makes things (more) flexible (whether
manual or with a framework)
- singletons are very hard to test and can cause unforeseen issues (e.g. the
one we have come across).
- statics as options are quite hard to deal with (as you've probably seen on
a previous post - still trying to get my head around how to change some of
these - I haven't forgotten it)


Chris



On 9 November 2010 18:12, DM Smith <dmsmith at crosswire.org> wrote:

> On 11/06/2010 12:13 PM, Chris Burrell wrote:
>
>> All,
>>
>> Just wondering if JSword provides a way of storing user information such
>> as favourite bookmarks, history, etc. on a user by user basis (i.e. for
>> potential use in a web application). I have a database that I could use, but
>> perhaps JSword already provides this?
>>
>
> No. We have a bookmark mechanism planned but it is geared for a single
> user. As you have found, JSword is not friendly for multi-user use. We
> should change that.
>
> In Him,
>    DM
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20101109/e5be87db/attachment.html>