I'd probably break it down into three sections. If a client app wants to deal with multiple sections, let it, but no sense burying clients that only care about employees under all the product and customer methods as well.
If you need to share sessions across multiple service objects (which you probably would want to), you'll probably want to add a 4th "security" service as well, that controls authentication and authorization for all the services. cheers, barneyb On 8/4/05, Dharmendar Kumar <[EMAIL PROTECTED]> wrote: > Hi Barney, > > Thanks for the insight. You are dead right on that. Also, I checked .net - > and it certainly does not support 'document' type. > > I will go with your recommendations. Thanks. > > On another note, about web services architecture - is it better to have all > your methods in one wsdl - or does it make more sense to have different > services for different modules in your app.? So if I have an intranet with > foll. modules: > > employees > customers > products > > Does it make more sense to have 3 diff. web services; each with related > methods? Or is better to have just one service? > > Thanks, > DK > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:213788 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
