class mapping terminology

[mikewse]

Ok, so here is a start of listing potential terminology for
  class mapping
  generated classes
  generated client-side classes
  mapped DTO classes
  __<fill in your suggestion here>__

First, we have registered a converter for our
  DataTransferObject class
  DTO class
  converted class
  __<fill in your suggestion here>__
on the server.

Then we add
  a mapping declaration
  client-side class info
  __<fill in your suggestion here>__
to the converter clause to generate a
  mapped class
  generated DTO class
  client-side class
  __<fill in your suggestion here>__
to be used in the browser.

Please help us find a coherent terminology by filling in more
suggestions!

Best regards
Mike Wilson

> -----Original Message-----
> From: joseph.walker@...
> [mailto:joseph.walker@...] On Behalf Of Joe Walker
> Sent: den 14 juli 2008 08:59
> To: users@...
> Subject: Re: [dwr-user] class mapping E3: Avoid downloading
> multiple declarations of generated JavaScript classes
>
> I totally agree about not liking the dto thing.
> We don't really have our own terminology in place here. We would use
> something like 'converted object' for people from a dwr.xml
> background. And DataTransferObject for people from an @Annotation
> background. I'm open to suggestions.
>
> Joe.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Joe Walker-3]

My 2c:

I suppose we have to acknowledge DTO as a synonym for converted class, since we've already made that 'mistake'.

If users don't know what a DTO is, it's only a single google away: http://www.google.co.uk/search?q=DTO&btnI=I'm+Feeling+Lucky

For when we add @javascript, we're already using the phrase Mapped Class. The downside of this phrase is that it's not obvious. It's not even obvious that this is a special type of converted class. On the plus side, we're using it already and it might be hard to change. 'Generated DTO' is slightly better, but I'm not sure
I too am open to suggestions, maybe we'll just need to see how things go.

Joe.

On Mon, Jul 14, 2008 at 10:32 PM, Mike Wilson <mikewse@...> wrote:

Ok, so here is a start of listing potential terminology for
 class mapping
 generated classes
 generated client-side classes
 mapped DTO classes
 __<fill in your suggestion here>__

First, we have registered a converter for our
 DataTransferObject class
 DTO class
 converted class
 __<fill in your suggestion here>__
on the server.

Then we add
 a mapping declaration
 client-side class info
 __<fill in your suggestion here>__
to the converter clause to generate a
 mapped class
 generated DTO class
 client-side class
 __<fill in your suggestion here>__
to be used in the browser.

Please help us find a coherent terminology by filling in more
suggestions!

Best regards
Mike Wilson

> -----Original Message-----
> From: joseph.walker@...
> [mailto:joseph.walker@...] On Behalf Of Joe Walker
> Sent: den 14 juli 2008 08:59
> To: users@...
> Subject: Re: [dwr-user] class mapping E3: Avoid downloading
> multiple declarations of generated JavaScript classes
>
> I totally agree about not liking the dto thing.
> We don't really have our own terminology in place here. We would use
> something like 'converted object' for people from a dwr.xml
> background. And DataTransferObject for people from an @Annotation
> background. I'm open to suggestions.
>
> Joe.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...