On Tuesday 27 September 2005 16:44, Normand Mongeau wrote:
> Well I want my back-end API to be protocol neutral, ie not tied to HTTP.
> Hence the desire to feed it only XML.
That wasn't the confusing bit. The question was where the XML is coming
from in the first place? If it's from the client,
On Monday 26 September 2005 20:15, Joshua Slive wrote:
On 9/26/05, Normand Mongeau <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> this is my first posting here, so please bear with me if I'm at the
> wrong
> place.
>
> I'm looking at Apache to be used as an HTTP server, to access a
> GemStone
>
On Monday 26 September 2005 20:15, Joshua Slive wrote:
> On 9/26/05, Normand Mongeau <[EMAIL PROTECTED]> wrote:
> > Hi All,
> >
> > this is my first posting here, so please bear with me if I'm at the wrong
> > place.
> >
> > I'm looking at Apache to be used as an HTTP server, to access a GemStone
>
Hi,
There are number of solutions to this. Generally I would use
something like Java, in a Tomcat, or maybe something like PHP.
One advantage of PHP over Java, is that you don't need a second
server running the application. The other advantage is
that you have much more control over the spec
On 9/26/05, Normand Mongeau <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> this is my first posting here, so please bear with me if I'm at the wrong
> place.
>
> I'm looking at Apache to be used as an HTTP server, to access a GemStone
> database at the back end. In my scenario all pages will be active.
Hi All,
this is my first posting here, so please bear with me if I'm at the wrong
place.
I'm looking at Apache to be used as an HTTP server, to access a GemStone
database at the back end. In my scenario all pages will be active. Ideally
I'd like Apache to convert HTTP requests to XML (pres