bric_soap

Today I was using bric_soap to generate some XML exports and
discovered
that doing so spawned an apache process that used a lot of
CPU. In fact,
performing a series of commands consecutively caused the
server to
crash!

I doubt this is normal behavior for bric_soap, or is it?

Chris

--------------------------

Chris Schults
Web Production Manager
Grist Magazine
710 Second Avenue, Suite 860
Seattle, WA  98104
Phone: 206-876-2020, ext. 204
Fax: 253-423-6487
<http://www.grist.org>


To sign up for Grist by email, the world's top environmental
news served
up with a sense of humor, click here: <http://www.grist.org
/signup/>

On Feb 13, 2007, at 4:55 PM, Chris Schults wrote:

> Today I was using bric_soap to generate some XML
exports and  
> discovered
> that doing so spawned an apache process that used a lot
of CPU. In  
> fact,
> performing a series of commands consecutively caused
the server to
> crash!
>
> I doubt this is normal behavior for bric_soap, or is
it?

It depends on what you're doing. But yes, if you do a bulk
publish,  
for example, you can easily crush your server. Use the
--chunks  
option to break things up.

Best,

David

I touched on this a few weeks ago with my post on link
checking, but 
I want to bring it back up.  I also want to specifically
solicit 
input from the higher ed people on the list:  How do you go
about 
maintaining intra-site link integrity with Bricolage?

On our campus there is the perception that we have a problem
with 
broken links and orphaned pages.  We suspect the Bricolage
solution 
is to only use related story links , and when a page
disappears, have 
a regularly scheduled bulk publish that goes through will
eliminate 
all broken related story links.  Of course, that also means
if a 
story is deleted, then there is still a period of time that
there 
will be broken links.

But, we also have the WYSIWYG, or the text area entry, where
inline 
link entry is possble.   How do others deal with that?  Do
you just 
instruct users to not use in-line links?  Do you have a
method for 
auditing those links?

Anyway, we are having discussions among ourselves as to the
best way 
to deal with the problem, and wanted to see how others
approached it.

Thanks,

Matt


-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537

On Thu, 5 Apr 2007, Matt Rolf wrote:

> I touched on this a few weeks ago with my post on link
checking, but I want 
> to bring it back up.  I also want to specifically
solicit input from the 
> higher ed people on the list:  How do you go about
maintaining intra-site 
> link integrity with Bricolage?
>
> On our campus there is the perception that we have a
problem with broken 
> links and orphaned pages.  We suspect the Bricolage
solution is to only use 
> related story links , and when a page disappears, have
a regularly scheduled 
> bulk publish that goes through will eliminate all
broken related story links. 
> Of course, that also means if a story is deleted, then
there is still a 
> period of time that there will be broken links.
>
> But, we also have the WYSIWYG, or the text area entry,
where inline link 
> entry is possble.   How do others deal with that?  Do
you just instruct users 
> to not use in-line links?  Do you have a method for
auditing those links?
>
> Anyway, we are having discussions among ourselves as to
the best way to deal 
> with the problem, and wanted to see how others
approached it.
>
> Thanks,
>
> Matt

I use Checkbot in a cron job for a couple of clients to
continually audit. 
You could add that as an action on publishing, sortof like
validating XML, 
although it tends to fail checking links to IIS servers.

Matt Rolf Wrote:
> I touched on this a few weeks ago with my post on link
checking, but
> I want to bring it back up.  I also want to
specifically solicit
> input from the higher ed people on the list:  How do
you go about
> maintaining intra-site link integrity with Bricolage?
>
...
>
> But, we also have the WYSIWYG, or the text area entry,
where inline
> link entry is possble.   How do others deal with that? 
Do you just

We don't use WYSIWIG, internal links are via related
story/media.  We
currently only manually audit.  Our CMS produced content is
pretty good
right now, but link integrity will degrade over time.  We
are looking at
automating our integrity check but have not settled on what
to use.  We
would like to automatically send broken link results to the
person(s)
responsible for the page.

- cameron