Sounds good, so basically we want to store it in the database. <div><br></div><div>Do we also want to store it in the cookie? I can see issues where for some reason persisting failed (say connection dropped, or user leaves before response is acknowledged). At which point, we end up having cookie/database out of sync.</div>
<div><br></div><div>An alternative would be store in the cookie if not logged on, and then persist in database if logged on (both for bookmarks and history). However, that does mean that user somehow needs to know that the bookmarks he his bookmarking or the history he is viewing might not get carried over.</div>
<div><br></div><div>Chris</div><div><br></div><div><br><br><div class="gmail_quote">On 22 March 2011 10:02, David Instone-Brewer <span dir="ltr"><<a href="mailto:Technical@tyndale.cam.ac.uk">Technical@tyndale.cam.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
Stupidly I hadn't thought about Bookmarks migrating from computer to
computer!<br>
I think I'd like my history to migrate too - to cope with the situation
of "I'm sure I read something yesterday about this".<br>
And the data is so tiny, we might as well make it endless, but only load
up the last ten with an option for "more".<br><br>
Seeing as I didn't think of it, I guess the average Jo won't think of it
either. <br>
It might be worth pointing this out at the signup stage: <br>
"Login to recall every passage you've read on any computer" -
or something like that.<br><br>
David IB<div><div></div><div class="h5"><br><br>
At 09:29 22/03/2011, Chris Burrell wrote:<br>
<blockquote type="cite">I agree that in some respects it
is strange. The rationale behind having to log on for Bookmarks and not
history is that history is something people expect to be able to clear
from their cookies. Bookmarks I would expect to be able to get back to at
a later date or on a different computer. If I were using a different PC,
would I expect to see my bookmarks and/or my history? My feeling is that
at least the bookmarks where I've intentionally said "bookmark
this!" I'd like to see all over the place. The problem is that if we
don't get people to log in, then we can't track their bookmarks across
anything but a cookie which is valid for that particular session/until
the cookies get cleared.<br><br>
Maybe it's a bit like a wishlist and the history on Amazon. With the
history you kind of expect them to track it With the wishlist it's tied
to your account a bit more.<br><br>
perhaps the history should be tracked server side as well. Happy to make
changes, but thought I'd try and explain why it is so, first. (obviously
the login prompt will come up for other features as well if they require
logging in).<br><br>
Any thoughts?<br>
Chris<br><br>
<br>
On 21 March 2011 20:02, David Instone-Brewer
<<a href="mailto:davidinstonebrewer@gmail.com" target="_blank">
davidinstonebrewer@gmail.com</a>> wrote:<br>
<dl>
<dd>Yep - that works nicely. <br>
</dd><dd>It seems strange though - you don't expect to log in for this. <br>
</dd><dd>What about putting registration at Install Bibles instead, and
reserve login for notes and other personal stuff? <br>
</dd><dd>You often have to give an email address to download stuff nowadays,
so it seems more normal. <br><br>
</dd><dd>The blinds in the middle work really nicely. <br><br>
</dd><dd>David IB<br><br>
<br>
</dd><dd>At 18:19 21/03/2011, Chris Burrell wrote:<br>
<blockquote type="cite">
<dd>There should be a new version of STEP on
<a href="http://crosswire.org/~chrisburrell" target="_blank">
http://crosswire.org/~chrisburrell</a><br><br>
</dd><dd>It should contain Bookmarks (well viewing them). There's some test
code in there at the moment, to automatically create a user in a
in-memory database:<br><br>
</dd><dd>username/email: t@t.c<br>
</dd><dd>password: password<br><br>
</dd><dd>The user can't do anything, so the data is not particularly
sensitive! You can register another user if you like (again, if i rebuild
this disappears, and it's not encrypted or anything like that at the
moment).<br><br>
</dd><dd>Once logged in, you should be able to see two bookmarks. The history
should now also be based on cookies, so that when you come back later,
whatever passage you were viewing is there. The data displayed under
"History" is stored in the cookie too and therefore persists
across sessions. History is stored in the in-memory database and
therefore is only available when you log in.<br><br>
</dd><dd>NOTE: There is a noticeable gap where the user can't delete a gap
(also, if the tomcat server gets restarted, or when i redeploy, then the
data disappears!)<br><br>
</dd><dd>Chris<br><br>
</dd><dd>_______________________________________________<br>
</dd><dd>tyndale-devel mailing list<br>
</dd><dd><a href="mailto:tyndale-devel@crosswire.org" target="_blank">
tyndale-devel@crosswire.org</a><br>
</dd><dd>
<a href="http://www.crosswire.org/mailman/listinfo/tyndale-devel" target="_blank">
http://www.crosswire.org/mailman/listinfo/tyndale-devel</a></dd></blockquote></dd></dl></blockquote>
<br>
<br>
_______________________________________________<br>
tyndale-devel mailing list<br>
<a href="mailto:tyndale-devel@crosswire.org" target="_blank">tyndale-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/tyndale-devel" target="_blank">
http://www.crosswire.org/mailman/listinfo/tyndale-devel</a>
</div></div></div>
</blockquote></div><br></div>