Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============6811078439346976260=="
MIME-Version: 1.0
To: "Ticket 6802" <6802@tickets.allura.p.re.sf.net>
From: "Dave Brondsema" <brondsem@users.sf.net>
Reply-To: "Ticket 6802" <6802@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #6802 ajax for last commit data
Message-ID: 
 <2df999a7fe2663caabae540ca14026fbcd3b408b.tickets@allura.p.sourceforge.net>
Date: Sat, 26 Oct 2013 04:25:45 +0000

--===============6811078439346976260==
Content-Type: multipart/alternative;
 boundary="===============3702122772164392173=="
MIME-Version: 1.0

--===============3702122772164392173==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit


---

** [tickets:#6802] ajax for last commit data**

**Status:** open
**Labels:** performance 
**Created:** Sat Oct 26, 2013 04:25 AM UTC by Dave Brondsema
**Last Updated:** Sat Oct 26, 2013 04:25 AM UTC
**Owner:** nobody

If a Last Commit Doc is not present for a tree view, it may take a while to generate that doc, so a better user experience would be to serve up the essential information immediately and use AJAX to fetch the last commit info.

Do we want this to be configurable per SCM type?  I.e. svn's last_commit_id might be fast enough all the time to not need to use ajax?


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============3702122772164392173==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/6802/">[tickets:#6802]</a> ajax for last commit data</strong></p>
<p><strong>Status:</strong> open<br />
<strong>Labels:</strong> performance <br />
<strong>Created:</strong> Sat Oct 26, 2013 04:25 AM UTC by Dave Brondsema<br />
<strong>Last Updated:</strong> Sat Oct 26, 2013 04:25 AM UTC<br />
<strong>Owner:</strong> nobody</p>
<p>If a Last Commit Doc is not present for a tree view, it may take a while to generate that doc, so a better user experience would be to serve up the essential information immediately and use AJAX to fetch the last commit info.</p>
<p>Do we want this to be configurable per SCM type?  I.e. svn's last_commit_id might be fast enough all the time to not need to use ajax?</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============3702122772164392173==--

--===============6811078439346976260==--