Plans
Raymond Camden
process is just pushing the zip to RIAForge and editing the XML file
used for version checking in the blog admin. (Oh and I'm going to add
some new screen shots to RIAForge. Anyone else think blogcfc.com the
site should have screen shots - perhaps under About?)
5.9.7.001 will be:
a) The bugs that will come from the new stuff.
b) Stats:
I'm going to move stats out of the public folder and build a richer
stats interface in the admin. I also plan on putting a few more quick
'dashboard' type stats on the admin home page. (For example, I'd love
to quickly see the most popular entries by comment activity). I plan
on looking at Mango and Wordpress and stealing ideas. (Wait, did I say
stealing out loud?) If folks have ideas or suggestions for this,
please let me know. I tend to get really turned on by charts so it is
a big deal to me but maybe folks don't feel like this is a big deal.
c) Mobile
When I asked Dave to build Mobile I told him specifically to work
within one folder. I'm cool with that but I want to move the config
into the core Blog config.
--
===========================================================================
Raymond Camden, ColdFusion Jedi Master
Email : r...@camdenfamily.com
Blog : www.coldfusionjedi.com
AOL IM : cfjedimaster
Keep up to date with the community: http://www.coldfusionbloggers.org
Raymond Camden
open a beer with me? Am I too excited about this?
Rob Brooks-Bilson
My main suggestion about stats is to move the view count out of the
main entry table. It will take some work to do this but it will be
better for performance (and make caching easier) in the long run.
Rob
Raymond Camden
count on a view it will run faster - but how would you track views
then?
Stephen Moretti
Stephen Moretti
Blog : http://nil.checksite.co.uk/
Twitter : http://twitter.com/mr_nil
Raymond Camden
<stephen...@gmail.com> wrote:
> The only "gotcha" I got was the gaAccount setting in the mobile ini.
> I did a cache clear in the admin, but obviously this only resets the
> application for the main site and not the mobile app.
> ?reinit=1 on the mobile url did the trick though and everything looks to be
> good. Loving the new look admin.
Yep - I'm definitely rolling mobile settings into main settings so
that a reinit there clears it all.
> By the way - the google click tracking is definitely working. I finally
> managed to spot some of the urls in my page view stats!
Nice!
> A thought occurs to me, can we get a setting for a reinit password please?
> :)
Surely you can't be serious. ?reinit=1 is virtually unguessable! ;)
Rob Brooks-Bilson
The design also complicates caching a bit as if you want to cache the entry, you're also caching the view count. By moving the count out to its own table, you could more easily implement partial page caching for everything other than the view count (if you wanted to do this).
If you take a look at the schema for Wordpress, you'll see that they don't store view counts. If you want view counts in WP, you need to do it via a plugin. Most of the plugins I've seen either store the views in their own table or in the wp_postmeta table (which allows you to store custom key/value pairs that are related to posts.
-Rob
Raymond Camden
<rob.broo...@gmail.com> wrote:
> Sure. The way the tables are designed now, the view count is stored in the
> same table/row as the entry that it belongs to. This means that every time
> you run a query to get an entry, you are also running a second query to
> write back to that same record. The read/write to the same table can cause
> you problems under heavy load. Granted most people using blogCFC probably
> aren't running into this issue, but it *could* be an issue.
Actually we don't do that - we use a session variable to record you
viewed the entry in your session. So it will only go up once. Of
course, robots won't keep the session.
> The design also complicates caching a bit as if you want to cache the entry,
> you're also caching the view count. By moving the count out to its own
> table, you could more easily implement partial page caching for everything
> other than the view count (if you wanted to do this).
I guess - but we aren't doing any caching yet in entry views. Haven't
seen a real need for it yet - even under load. The # of queries per
request should be pretty low (worked on that about 6 months ago).
> If you take a look at the schema for Wordpress, you'll see that they don't
> store view counts. If you want view counts in WP, you need to do it via a
> plugin. Most of the plugins I've seen either store the views in their own
> table or in the wp_postmeta table (which allows you to store custom
> key/value pairs that are related to posts.
Well, I'm definitely adding custom field support. Maybe we can take a
wait and see approach on this and consider putting views there too
later.