[seam-dev] Naming convention and package organization advice
Antoine Sabot-Durand
antoine at sabot-durand.net
Sun May 1 16:15:51 EDT 2011
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.
Antoine
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 ;)
>
> ~Lincoln
>
> On Thu, Apr 28, 2011 at 9:53 AM, Antoine Sabot-Durand <antoine at sabot-durand.net> 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.
>
>
>
> Antoine SABOT-DURAND
> ---------------------------------------
> Twitter ; http://twitter.com/antoine_sd
> LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110501/edf8ff4a/attachment.html
More information about the seam-dev
mailing list