Just that it sounds like a bug in the specification.
While we're discussing this, I dislike the fact that this spec re-uses
service.pid but places additional restrictions on it. I would have preferred
using a different name such as monitorable.pid.
Greetings, Marcel
On Nov 21, 2011, at 12:36
Does nobody have any thoughts on this?
Hi there,
In 119.2 compendium, Version 4.2 I read that the length of the
monitorable-pid must fit in 32 bytes when UTF-8 encoded. (Given that
all the characters allowed in the symbolic-name syntax encode as one byte,
this would appear to mean that the
I very quickly checked the RI. From what I could see there the limit is 32 so I
would too suspect a bug in the spec. I will open a bug for this.
One could perhaps also argue there should a public constant for this limit.
Regards,
Christer
--
Christer Larsson
Makewave, http://www.makewave.com
Maybe the work around (this will give a rough estimate) would be
to look at the resident objects within a given bundle (include all
the objects inside it)? Not sure if that's also possible.
Objects don't reside in bundles. Objects live in the heap. Objects are
instances of classes.
