Mark Martin wrote:
More information can be found at http://opensolaris.org/os/community/web
Been there, seen it, thanks. But again, that's not so germane to where
I'm trying to delve unless you folks think so.
Insofar as we are trying to provide an integrated web presence for
opensolaris development, it is.
By the way, 404 for
http://opensolaris.org/os/community/web/restructuring.html
Fixed, thanks,
ARC case files make up over 50% of the content on opensolaris.org, and
we have a strong suspicion that they are a significant contributor to
the instability we are seeing. If that proves to be the case, we'll
be addressing that issue with some urgency.
So to me, it seems like the ability to generate content dynamically is
probably the only thing that'll work long term. At a minimum, some sort
of ability to allow users to generate and satisfy queries, and provide
top-level case listings without throwing `ls -R` into the navigation.
Does it need to integrate with the new wiki?
Actually, generating the content dynamically *is* the problem. We get
heavily spidered by search engines, virtually all the site content is
dynamic, much of the ARC content is only ever visited by spiders and
that's one suspect for what is killing the site - hence tomorrow's test.
If you needed to access content via a HTML form, it can make it hard for
spiders to find it - and we *like* being spidered, it's just at present
we are being loved to death.
I guess that presupposes that any viewer on the case repository must be
able to interface with the VCS if there is one.
At present there isn't.
As for addressing the ARC content=instability issue short term, may I
ask what the tentative plan of attack is, or have you not gotten that far?
We are going to see if stopping access to the ARC data for 24h helps.
If it does we'll probably move it elsewhere under OSO. But we need the
evidence first, hence the test.
--
Alan Burlison
--
_______________________________________________
website-discuss mailing list
[email protected]
