The key is "and is serializable" right? Otherwise, you'd just call it Cow. But you want to somehow imply that it can be serialized with the name? Python folks refer to the process of serializing as 'pickling'. I think that's rather tongue-in-cheek. But maybe it's a hint for your.
Maybe you should call your class Burger. Or maybe: public class Cow implements Burger.
Where Burger is a marker interface, a la 'RandomAccess' in the new 1.4 Collection classes. Hey wadya know, my SCJP works!
Originally posted by Mike Curwen: Python folks refer to the process of serializing as 'pickling'.
It's my understanding that the term "pickling" way predates Python. I hope I'm not hallucinating this, but I think even Oracle has some procedures called "pickling" (which shows a certain amount of levity not usualy expected). Sorry for the hijack, Paul.
Yes, VO is "value object" and DTO is "data transfer object". This is something that would carry typed data from the server to the client in a lean class. I know which one I prefer, but I want to get a feel for what's used the most out there.
Joined: Mar 09, 2001
OK, maybe I'm being a little too desciptive in my naming, but if the class is meant to carry cows how about . . . MeatWagon Seriously, CowDTO is my choice if there are other Cow classes involved.
Do I dare move Paul's topic over to J2EE/EJB where it's more approrpiate... Surely there must be a J2EE Blueprints naming convention guide out there somewhere. Me too busy listening to Joan Armatrading to go lookin'