[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [higgins-dev] Updating Password with IdAS
|
Does this seem like a reasonable direction? Anyone have an opinion on the type we should use for extendedArgs? I'm coming from a background where Args would be defined to have to properties:
??? identifier; some globally unique identifier which can be used at runtime to identify the type of the arg, and also could be used to tie the arg to documentation somewhere. Note that with reflection, this isn't needed (afaik).
boolean criticality; // true when the caller expects the cp to support this arg (and expects an exception if the cp doesn't support the arg). false when the cp is free to ignore the arg.
Object payload; // the actual arg.
If we don't need the identifier (which I don't think we do), and don't need the criticality (this _has_ caused some confusion in the world I came from), then extendedArgs could be an Object[].
Jim
>>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 8/24/07 7:38 PM >>>
Getting back to this after almost a month :( I've added this page that summarizes where we left off.