Sounds sensible however a service being a component doesn't really tie it down for me much. I guess there is no clear boundary.
On 6/2/05, belaran <[EMAIL PROTECTED]> wrote: > The way i see it a "service" should be component... > For instance, > For a simple web app using hivemind, you could a DAO service to access the > database , a bizness service that's actually those the work and maybe a third > service, that'll realize the XML/XSL transformation. > That's my point of view, but i'm still a beginner, so maybe i'm wrong.... > > Belaran > > > 2005/6/2, Glen Stampoultzis <[EMAIL PROTECTED]>: > > > Was just wanting to get some peoples opinions on what sort of things > > should be made into hivemind services? > > > > It seems to me that it would be pretty easy to go crazy and make all sorts > > of services but I'm thinking that would probably be a bad idea. Where do > > you stop? I'd be interested in hearing real life services people have > > created. > > > > Regards, > > > > Glen Stampoultzis > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
