On Jan 16, 3:41 pm, Derek Steinkamp <[EMAIL PROTECTED]> wrote:
> Yeah, #3 is probably what I'll end up going with.
>
> The files in question are a standardized lab-wide header/footer/css.
> They don't change often, but they may in fact change and I would like to
> keep current.
>
> Good point made in #2, I didn't really think of that. I just wish HTML
> had something in it similar to the <img src="..."> tag that you could
> point at a site and directly embed its code... this would work nice as
> the client is doing all the fetching.
You can do that to some extent with an iframe or an object tag.
> I suppose doing a simple client-side fetch & print in javascript could
> work as well.
Right. Really depends on the content/purpose of the file and what
level of usability you need (e.g is it OK to assume that all your
users have Javascript enabled?, etc..)
If the included file has template tags that Django needs to
preprocess, then you will obviously need to bring the file down to the
server as you were thinking.
Anyway, good luck.
-Rajesh
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
