Hello,
I had the same problem, but not a clue how to implement this.
After Donald mentioned that the template system uses pluggable loaders,
I spent some time to create one for my own use. It's very basic, but at
least I believe it demonstrates how to create a template loader.
Kurtis, you can fin
On Wed, Oct 19, 2011 at 5:17 PM, Kurtis Mullins
wrote:
> Good idea. I'm going to check out MongoDB for this. Looks like there's
> already some Django tools for it out there.
>
> On Wed, Oct 19, 2011 at 5:57 PM, Donald Stufft
> wrote:
>>
>> If I wanted maximum performance from a distributed on the
Good idea. I'm going to check out MongoDB for this. Looks like there's
already some Django tools for it out there.
On Wed, Oct 19, 2011 at 5:57 PM, Donald Stufft wrote:
> If I wanted maximum performance from a distributed on the fly template
> system. I'd probably store them in a fast document db
If I wanted maximum performance from a distributed on the fly template system.
I'd probably store them in a fast document db.
On Wednesday, October 19, 2011 at 5:54 PM, Kurtis Mullins wrote:
> Very true, I could definitely implement it as a pluggable loader. I'll try to
> find the DB Template L
Very true, I could definitely implement it as a pluggable loader. I'll try
to find the DB Template Loader too. I'm mainly concerned with this being a
large bottle neck for our front-facing pages so I'm not sure which path to
choose. Maybe some R&D is in order :) Thanks!
On Wed, Oct 19, 2011 at 5:5
The template system uses pluggable loaders that can locate a template based
upon it's name. So using that you can store your template anywhere. There is
already an app for storing templates in the db, you could easily make one to
store it somewhere else as well.
On Wednesday, October 19, 2011
6 matches
Mail list logo
