[GeneralDiscussion] Re: zope/plone article

Morning Niall,

I'm glad you're digging into this. First, fyi generally Zwiki's  
philosophy is to "just work" for the mainstream 80% of uses, and not  
prevent further customisation but not fill up the codebase and  
development time with it either. Now -

The caching investigation is very much appreciated, I assume you're  
referring to some issue page or other. It's over my head just now and  
not causing me problems in daily zwiki usage so I'll have to say  
"patches welcome".

> Yes. The masterinclude file defines a set of links in RST format. All
> other files in the wiki then use those links without having to define
> them individually. Now to update the links one simply changes
> masterinclude and the rest of the wiki updates itself.

I see, thanks. I guess this might be important if your wiki has a lot  
of outgoing links to the same site(s). This is exactly what  
RemoteWikiLinks are for. I think you don't like those because the  
definitions are not gathered on page, and because you don't like the  
linking syntax (you must have come up with something equivalent  
though ?)

FWIW, in the past I found RemoteWikiLinks weren't worth the bother,  
because it was one more non-standard linking scheme for people to  
learn and it obscured where the link really went - ordinary bare urls  
or manual hyperlinks were clearer.

If you're into RST, maybe another option is to have the format method  
in rst.py append the contents of the masterinclude page before RST  
rendering. And on that page, define the link targets, RST footnote- 
style. This forces you to define each individual url though, not just  
a base url like RemoteWikiLinks. So probably not worth it.

> I am running zwiki on plone but behind a CacheFu controlled "varnish"
> reverse proxy - varnish is very seriously impressive and as I
> mentioned in my "Setting up Plone on a low end VPS" guide, my
> piddling 256Mb RAM VPS can handle being slashdotted (>1000 concurrent
> requests) with varnish running despite it using around 400Mb of RAM
> (192Mb of swap!)

Yes it was good to see your detailed numbers in your write-up.

> To make use of varnish, you need a minimum of conditional HTTP
> working. I turned on conditional HTTP gets - the zwiki code reports
> the datestamp for the page which is to be expected, but this ignores
> the masterinclude. I can't see any way of overriding this date in the
> zwiki source - would adding this facility be a good idea as who knows
> what templates may do with rendering zwiki pages? If they had a
> publicly available method to call it would be useful.

Yes that might be worthwhile. Though it's a bit of a small niche right  
now.


--
forwarded from http://zwiki.org/GeneralDiscussion#[email protected]