Re: More robot problems with WO sites
Re: More robot problems with WO sites
- Subject: Re: More robot problems with WO sites
- From: Chuck Hill <email@hidden>
- Date: Fri, 1 Apr 2005 12:44:06 -0800
On Apr 1, 2005, at 12:30 PM, Baiss Eric Magnusson wrote:
I have finished the work on <nwSufis.org> and now I get zero sessions
being created, the site being all done with DirectActions until a
Login occurs.
I get an average of 1 robot query per minute, which I can view by
looking at the Transaction count.
However, even with moving the TravelLog WO site out of a re-direct
call I am getting about 10 sessions created each hour, they drop off,
but at the end of the day there are over 30 TravelLog sessions on
JavaMonitor.
First, what is the problem with session creation? They are not in and
of themselves heavy weight objects. Keep the session timeout (period
of user inactivity before termination) low and drop the page cache size
to limit memory usage. The defaults are something like an hour and 30
pages, way too much for most situations. Could it be that you have a
bug in your code that is preventing sessions from being terminated?
Exceptions raised in the Session() constructor, awake(), sleep(),
terminate(), and finalized() can cause problems with this. Ensure that
nothing in those methods can throw an exception.
Here's what the robots go to from
<http://CascadeWebDesign.com/travel.html>
<FORM method="post" name="startPage"
action="http://www.CascadeWebDesign.com/cgi-bin/WebObjects/
TravelLog.woa/wa/default?userId=1001">
And all the links on that page are session based, component actions.
From what I can tell, none of them need to be component based. I did
not click too far, it but looks like the whole thing could be direct
action based.
And my robot file is:
Disallow: /WebObjects/
Disallow: /photos/
Disallow: /travel.html
Disallow: /cgi-bin/
Not all spidering applications will obey this.
I even have in <travel.html> the line
<META NAME="robots" CONTENT="nofollow">
So it seems to me that the only solution to having a WO site hosted by
a server immune to overload is to make that site a DirectAction site
until a legitimate user comes along, i.e. one that you want to give
edit privileges to.
We have a large, heavily used, direct action based application that
always creates sessions. We've never had a problem with it. We use
direct actions to allow ease of bookmarking. What sort of overload
problems are you experiencing?
Question: how do blogging sites work where they allow everyone to
edit, from my experience the server would get bogged down with
extraneous sessions?
Probably most of them are not written using WO. :-) But your comment
about "get bogged down with extraneous sessions" makes me think
something else is wrong in your app.
Chuck
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden