gSoap

[kenny]

That's great it works.

So, all it does is generate xml files to be tranferred over http[s]? Or does it also request xml files from outside sources (as if it was an api). Sorry, the only experience I have with this is the youtube api where I send them the video id, and the respond back with all of the meta data in xml format... something like that?

Also, I don't know why you would want it reimplemented in D, when a C one exists... At the moment, I use tons of C mixed with D, and it works great... just remember to .dup your strings :)

Example for me... Making a web server in D is difficult, so instead I just stripped shttpd and stuck D as the frontend. It works great. On my laptop, I can generate 2-3k D generated pages per second (average 60 opcodes per page from the template engine). Quite frankly, D sucks for some things -- like sockets for example. For some reason, I can always get them to go faster in C than I can in D. The other thing is threads. locking mutexes and not having tons of problems works perfect in C, but in D, I want to kill myself. If I use the standard threads, it issues a USER1/USER2 signal every time the gc is run (extremely annoying in gdb). If I implement my own threading using pthreads, I sometimes get undefined behaviour... it just seems annoying is all, when in C, I know exactly what is happening.

I would just make D the frontend, and let C do all of the work. It's saved me a lot of hassles in the past.

James K Smith wrote:
> "kenny" <funisher at gmail.com> wrote in message
> news:f8u7bc$nf0$1 at digitalmars.com...
>> No, I definitely am using D for commercial grade web services but not with
> gsoap... I'd actually never even looked into soap, so I looked through
> gsoap's website... I'll be honest, I have no idea what it's talking about...
> 
> What I meant by "commercial grade," was implementing a standard protocol
> over https. Most any shop no matter what the dev tools can shoot me soap
> messages through a client after I publish the wsdl for the calls. It would
> be great to have something standard like this implemented in D. xml-rpc
> would work as well. Add https or tls to the mango http server, and it's a
> starting point. Http without security and authentication is not much value
> for commerce of course.
> 
> In the meantime though, gsoap does all this stuff in straight C.
> 
>> It shouldn't be too hard to bind it though. It appears that everything
> goes through C interfaces. You could also write some sweet sweet templates
> to automate some of that nonsense on the page in the examples sections
> (seems like a lot to do very little).
> 
> Doing some work with bcd.gen now.
> 
>