WebDAV Interface

[emhill]

Not sure if this is the correct forum or not but we are needing some information on interfacing from the iSeries to a WebDAV system. If anyone is doing this could you give us some helpful hints or info?

Thanks in advance and sorry if this is way off topic!!!

[Scott Klement]

Not sure if this is the correct forum or not but we are needing some information on interfacing from the iSeries to a WebDAV system. If anyone is doing this could you give us some helpful hints or info?

I have not done it, but from what I know about DAV, it's merely a set of additional HTTP methods. You could potentially use a tool like HTTPAPI to do this -- though, depending on the exact need, HTTPAPI might need a little tweaking to make it work.

Or, even easier, if there's a WebDAV library written in C, Java, or PHP, you could potentially just that on IBM i, and interface it to your RPG programs.

Thanks in advance and sorry if this is way off topic!!!

Yeah, I guess you're right that this isn't related to Profound UI, so is off topic for this particular sub-forum. But, this site has an RPG sub-forum as well.. it'd be 100% on-topic there, assuming you're looking to use WebDAV from your RPG programs, that is.

Of course, if we wanted to keep this on topic for "profound ui", I could suggest that you create your own custom WebDAV widget that can be dragged/dropped in the designer. That might be fun! (For a geek like me, anyway). But it's probably a lot easier to implement on the server-side.

[Scott Klement]

What are you using WebDAV for? Do you have a specific application that uses it, like a calendar (though, you'd probably use CalDAV for that)? Or is this some unique application?

[emhill]

Scott,

It is a unique application for the diesel engine business. Funny that I just started having a look at the HTTPAPI command....

Thanks!!!!

[Scott Klement]

The commonplace usage of HTTPAPI involves only the GET and POST methods, so that's what you'll see a lot about.

However, within the (lower-level) persistent routines, there's a routine called http_persist_req that can send other operations besides GET and POST. AT the moment, it's not expecting the WebDAV extensions, so a bit of code mods would be needed (primarily in the do_oper routine) but these should be small changes.

So, this could get a bit complex for someone who isn't familiar with HTTPAPI's internal coding structure -- but, of course, I'm the principal author of HTTPAPI, so it's pretty easy for me.