Good suggestion, Mike, that should help. :) I actually already moved the
configuring section down below the Mr. Bond example anyway because I
think people mostly are wanting to get into working with it, so it makes
sense to give them a working sample before throwing optional stuff at
them. :) But I'm gonna add the optional note in the section title too.
> Where should the agents be declared and what scope would you
> recommend? Thanks for your help.
Well the agent should definitely be placed in your application scope --
that way it can still cache content if it's unable to connect to the
service for any reason (like, the service isn't installed being the most
common reason). For the agent's context (note the distinction, since
only Railo has a "cluster" scope yet) ;) I would leave the agent's
context as application (default) for running the examples. I'm actually
not sure if I've tested the Bond example, so I can't say off-hand if it
has any typos in it.
Anyway, thanks for helping us on the project. :)
--
s. isaac dealey :: AutLabs
Creating meaningful employment for people with Autism
http://www.autlabs.com
ph: 817.385.0301
http://onTap.riaforge.org/blog
Yeah, I've been wondering about some of the interface decisions myself
and not entirely sure how to address some things that I thought might be
issues.
> Also maybe the "Agent Detail" tab should be present all the time
> instead of appearing and disappearing, it could be disabled or if
> clicked display a message saying, select an agent from the agent tab.
> (could have agent tab linked, in the message)
Or maybe we could use a side-nav or breadcrumbs on the agents tab. So
you would stay on the agents tab, but you'd get a sub-nav with
list -> detail -> content
Thanks for the feedback, Mike! :)
Oh oops, yeah, I think there might be a blog entry about that... I
realized a couple weeks ago that there were some bugs in the agent-size
feature. And those were in my samples too... getHeadCount() was removed
- the Agent and the Nanny both have getSize() instead. The service and
the storage CFCs are both using getOccupancy() because it was
duplicated functionality with getHeadCount(). So it sounds like you
might not have quite the latest build.