Re: Web Apps - Which Way to Jump
- From: Andrea Raimondi <rainaple@xxxxxx>
- Date: Sat, 25 Feb 2006 19:45:54 +0100
Christopher Burke wrote:
Rather than describe the projects in alot of detail - I was wondering if people could give me an idea of each of the web technologies, and what you might use them for.
You have several possible choises, imho, depending on the
kind of situation you're in:
1) Own server
2) Hosting
With "own server", I mean one where you have full control and aren't
bound by specific limitations, unlike hosting.
Side note before starting: both Win32 and dotNET world have
interesting Object Persistent Frameworks to help you separate your
business logic from persistence - worth giving a shot.
You'll find InstantObjects for Win32 in the companion DVD.
OWN SERVER(Win32 world)
-----------------------
You have the broadest of choices.
One option is to have a webservice running either on IIS or as a
service(see http://www.remobjects.com for this), then have your
site access this service.
Advantages: 1) You can access it from anywhere, having for
example specific native clients for the
platforms you want to support.
2) Abstracts you from the underlying code
3) Scales much better( you can have a central
balancer and redirect calls to different servers
running the same application)
Disadvantages: 1) Splitting structure means mantaining different
applications, with all that this involves
2) You have to take care of who connects to what,
this can become a bit tricky if things aren't
done in the proper way
3) You have to consider the basic security issues
(like DoS, DDoS, etc)
4) It might get "involved" if you want to have HTTPs.
Then you could have your own webapplication.
This issues several other choises.
- WebBroker: you know it.
- Intraweb: good if you have a controlled environment,
less good if you're opened to cyberspace.
This is because it's tough to support all
browsers of the world, while plain and
simple HTML files do it brilliantly.
Since you have Ent edition, you're also
provided with IW Application mode, which
basically is a webserver where your app
gets executed. Wonderful for debugging.
- WebSnap: Easy to use like the Space Shuttle, at least in Delphi 6.
Dunno if it got better beyond(only having Pro right now).
HOSTING(Win32 world)
--------------------
Choises get tough here.
Most hosters won't allow ISAPIs, making it quite difficult to use
webservices of any kind. Same goes with WebBroker and Intraweb.
DOTNET WORLD
------------
Here the distinction is basically useless because, apart from
dotNET remoting being available for an own server, doesn't
change much.
Your only choice is ASP.NET - and not a bad one if properly
designed. It will have the *huge* drawback that you need to
face the dotNET framework, which really isn't a piece of cake.
There's - however - one possible very good reason to go for it.
You have ECO which undoubtedly has many handy features(all the
services provided and the possibility to create your own) and a
very clear implementation path (you'll use Together modelling for it),
plus a newsgroup where knowledgeable people will help you get up to
speed.
Last, but not least a *very* appealing reason for choosing dotNET is ready made implementations of EBay and PayPal SDKs, which could be
useful for your shopping.
Thanks for your help.
HTH,
Andrew
.
- References:
- Web Apps - Which Way to Jump
- From: Christopher Burke
- Web Apps - Which Way to Jump
- Prev by Date: Re: General approach to HTML data mining
- Next by Date: Re: If you think to abandon Delphi - Remember why you chose it !
- Previous by thread: Re: Web Apps - Which Way to Jump
- Next by thread: Re: Web Apps - Which Way to Jump
- Index(es):
Relevant Pages
|
