Pact support for streaming protocols?

[Jeff Doll]

Are there any plans to implement pact over streaming using websockets?

[Michel Boudreau]

It has been talked about. Personally, I think this is the natural progression of the web and Pact itself, however, we want to make sure that we have a great product to start with that simply does json over http for now. Once happy with that, I definitely think that steaming is the next logical step.

What are your thoughts?

On Tue, Jun 28, 2016, 10:59 AM Jeff Doll <jeff...@workiva.com> wrote:

Are there any plans to implement pact over streaming using websockets?

--
You received this message because you are subscribed to the Google Groups "Pact" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pact-support...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Doll]

I agree that this is the natural progression. We're looking at using Pact but currently would be restricted to implement over fallback protocols due to lack of websocket support.

[Michel Boudreau]

Thanks for letting us know that it's a blocker for you.  The more support we get for it, the quicker we'll get to it :)

Any other form of feedback and/or contributions would be greatly appreciated.

M

On Tue, Jun 28, 2016 at 11:09 AM Jeff Doll <jeff...@workiva.com> wrote:

I agree that this is the natural progression. We're looking at using Pact but currently would be restricted to implement over fallback protocols due to lack of websocket support.

--

[Matt Fellows]

This is something we've been discussion for Pact Spec v4+. Currently, we only support HTTP (and generally only JSON payloads). You could envisage a future where MQTT and others come into play, and in fact, I'm currently on a project where raw TCP would be great.

Out of interest Jeff, what language implementation are you using? There are workarounds that can be applied in Pact JVM (and probably in Pact JS) that might be able to work around the protocol and let you test the payloads. 

--

Matt Fellows
- http://www.onegeek.com.au/

[Jeff Doll]

At the moment, we're considering implementations using go, jvm, and considering some potential uses for the dockerized provider verification. We've love to see a dart library, but recognize that dart isn't a highly demanded language yet. We've looked at patching the go daemon to add websocket support, but we're still weighing our options for validating our service contracts at the moment.

[Matt Fellows]

In theory slotting websockets into the Go or Js should be fairly straightforward but it would only support json payloads  (which I'm guessing is probably OK anyhow).

On 29 Jun 2016 12:05 am, "Jeff Doll" <jeff...@workiva.com> wrote:

At the moment, we're considering implementations using go, jvm, and considering some potential uses for the dockerized provider verification. We've love to see a dart library, but recognize that dart isn't a highly demanded language yet. We've looked at patching the go daemon to add websocket support, but we're still weighing our options for validating our service contracts at the moment.

--