Has anyone else found the "encoder" concept in Loop misleading? I'd
suggest renaming it to "mapper".
I see a "mapper" as being something that maps between one thing and
another, eg. between a key and an object.
An "encoder" is something that converts data between formats without
loss - all the data is there and only its format has changed (eg. from
chars to binhex).
In fact, the Loop component actually uses both - it asks our "mapper"
to give it the key of the data, then it uses its own internal
"encoder" to encode the keys into a hidden field. On submit, its
internal "encoder" decodes the hidden field, then gives the keys to
our "mapper" which has to return the corresponding object, possibly by
going to the database.
I raise this thought because I found the name "encoder" blurred my
understanding of what I really had to provide and how it would affect
what went to the client. I'd suggest "encoder" becomes "mapper", and
(even more controversial?) PrimaryKeyEncoder becomes PrimaryKeyMapper.
Has anyone else found confusion in this?
G.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
