I have not done this myself though have a IVR system that we plan to
migrate to using webservices call when the next software upgrade is release
that supports .NET . Why have the IVR phone system us webservice to work
with the DB. Simple one place for the logic. The our IVR system uses the
same business logic as our web application and being able to keep the
business logic in one place would be a big win.
I do know of one software that has been written in a manner as you
are talking about. Artifactsoftware.com From what I under stand there
entire application is build on webservices(.NET) but they have a web version
of there application and a desktop application and both make calls to the
webservices to do all db and business logic interaction. I meet one of
there developers a year or so ago when he was working on the web version of
there application he was only allowed to interact with the webservices and
not the DB even though the webservice and the DB were going right there.
This allowed them to reuse all of the DB and business rules they had already
built and leave one place to maintain.
The one pro and con to this that I can is if you make changes to
your webservices that require changes to code that calls them you then have
to maintain that code and if you have multiple front ends you then have more
work. But if you have well defined and loosely coupled interface between
the front and back end then this should not be to large an issue.
I think I may still have the card for the developer at Artifact if
you would like to talk with him. Email me off list if you want his contact
info.
Daniel D.
-----Original Message-----
From: Christian Cantrell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2003 12:08 PM
To: cfc-dev
Subject: [CFCDev] web service API
I'm thinking of building an application that will have both a Flash and
HTML interface. My initial thought was to encapsulate all my business
logic in components which can be accessed by ColdFusion, then create a
web service or Flash Remoting facade for the Flash interface. Another
approach, however, would be to only create web services, and have both
the Flash and ColdFusion interface use the components as web services.
The advantages of an architecture like this are:
- Simplicity. Just one external interface for both CF and Flash.
- Distribution. I could potentially run the CF interface on a
different server than the CF web services (though I must admit, I don't
foresee a need to do something like this, but it still seems like an
interesting option to have).
The biggest disadvantage would probably be performance, although at
this point, I don't have a good sense of how much additional overhead I
would be dealing with.
What do you guys think? Has anyone done something like this?
Christian
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[EMAIL PROTECTED]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
