Hi Martijn,

Today, it seems, many devolopers are spending time building middle
tiers that do nothing more than bridging exactly what a "published
proc" would do.
It would certainly be great to be able to call web services,
protocol and driver independent, from all various front ends you
work with. Web services, for those that havn't tried them, can
return as complex datatypes as (even nested) datasets, making them
great as database interfaces.

As you say, IIS is certainly involved, handling the requests. And
maybe this functionality is better implemented as an 'add on' to FB.
But a generic solution would be much sweeter :)

/Martin

--- In Firebird-Architect@yahoogroups.com, "Martijn Tonies"
<m.tonies@u...> wrote:

> Hello Martin,
>
> > Searched the archives, but didnt find anything in this area, so..
> >
> > Are there any plans to add functionality to publish procedures as
> > web services? I think this is a upcoming feature in MSSQL, and,
> > regardless of that, it would be a fantastic FB functionality,

making

> > it even likelier to be the choice for new users.
>
> I'm not sure - but I think MS SQL does this via .NET procedures
> and in combination with IIS and the like, right?
>
> Either way, by itself, Firebird doesn't have close connections to
> any other services, unlike MS with its products.
>
> Therefor, I think just "publishing as webservices" by itself

doesn't

> mean much.
>
> If I'm completely wrong, please do set me straight :-)
>
> With regards,
>
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL

& MS SQL

> Server.
> Upscene Productions
> http://www.upscene.com