Hi Guys (and wurley),
Thanks for the explanation on Bug #2875788, but with the bug closed, I can't
easily respond. I thought I had been clear on what I was observing, and
seeking information on whether that was intended behavior or not. I suppose it
is, but I just wanted to get some finer detail.
For starters, I didn't think that clicking on an OU in PLA 1.1.0.7, and having
the right-hand window open up with its properties was necessarily considered
"editing", but I suppose in a way, it is, and PLA 1.1.0.7 is just making some
assumptions and loading the default template (which is no template at all) for
the OU objectClass.
So under PLA 1.2.0.4, this assumption seems to be gone, and 1.2.0.4 seems to
favour better flexibility, thus the change to let you choose a default template
to go with that particular OU (because it is entirely feasible that someone's
custom setup extends the base schema of an OU to include additional
functionality). I just didn't see this change documented anywhere, so when I
switched from 1.1.0.7 to 1.2.0.4, this was essentially having a curve ball
thrown at me.
So, knowing this, is it safe to assume the following?:
1. That the behavior I saw in PLA 1.1.0.7 was just the way that branch of the
code functioned, and 1.2.0.4 is designed with more flexibility in mind, thus
the change to make it ask you to pick a template?
2. Since the templates in PLA 1.2.0.4 are considered "samples", is it correct
to assume that one isn't supposed to use PLA 1.2.0.7 "out of the box"? I.e.,
one needs to do a bit of work to tweak these sample templates (or write new
ones) to fit one's environment? In this regard, 1.1.0.7 seemed to function
better as an "out of the box" release.
The end purpose of this, is I have to write documentation for my environment,
and that includes documentation for this software, so that others in my
environment can understand what exactly is going on. Understanding any
behavioral changes between 1.1.0.7 and 1.2.0.4 allows me to write better
documentation, hence the inquiry (and the bug was just a knee-jerk reaction --
I really should have inquired on the ML first).
Also, a minor thing, but I am noticing a CPU spike in 1.2.0.4 when editing an
object for the first time. 1.2.0.4 does seem to cache data more aggressively,
too, so perhaps I am seeing this. But on a dual-core 64bit system w/ 8GB of
memory, my CPU meter hits 70-80% for several seconds before calming down. I
didn't notice this under 1.1.0.7.
Thanks!,
--J
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
phpldapadmin-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/phpldapadmin-users
