So "service" it will be. thanks


Le 1 mai 2011 à 22:44, Shane Bryzak a écrit :

On 02/05/11 06:15, Antoine Sabot-Durand wrote:
These bean are in the API. I Thought about Twitter or Facebook name but I'm not sure it won't be confusing since I already have @Twitter or @Facebook qualifiers. Perhaps I'm taking too much precautions here...

These beans manage the high level API to interact with social network. They contains methods like updateStatus() or getTimeLine() for instance.

I think that the 'Service' suffix might be more intuitive for these classes (i.e. TwitterService).  It's also in accord with the function of the class, being that they interact with social networking 'services'.



Le 30 avr. 2011 à 16:29, Lincoln Baxter, III a écrit :

Are these beans that developers will be interacting with / API? Or are they an implementation detail?

If the former. Why not just use "Twitter" or "Facebook" ?

"Handler" isn't bad, I'm not sure there's a great word, what is the purpose of these beans. e.g: what do they do? that might help us figure out if the name is appropriate, or if we should try to forge a little more ;)


On Thu, Apr 28, 2011 at 9:53 AM, Antoine Sabot-Durand <> wrote:
Hi Team,

in Seam social I created bean to deal with social network. I named those Bean with "Handler" suffix : i.e. TwitterHandler. I choose this over "Service" or "Controller" but as there will be other Seam module dealing with high level functional services, I prefer check this naming convention with you. Sharing the same naming convention across modules to have something homogenous is something important.

Twitter ;
LinkedIn :

seam-dev mailing list

Lincoln Baxter, III
"Keep it Simple"

_______________________________________________ seam-dev mailing list