ejpbruel/factor

factor's Issues

We need a way to integrate Factor with the devtools server.

Now that we've demonstrated Factor as a proof of concept, we need to come up with a viable migration path. Ideally, people should be able to use Factor on an opt-in basis, without any changes to their existing actors. Jryans suggested he may have some ideas to accomplish this.

If using Factor on an opt-in basis turns out to be impossible for some reason, the next best thing would be to reimplement the protocol.js API on top of Factor, so that most of the existing devtools actors can be used with no to minimal change.

An additional requirement is that we should not pollute the Factor repository with concepts from the devtools server: Factor is intended to be a standalone library. It should either be hooked into the existing devtools server, or the devtools server should be layered on top of it.

I'm opening this issue to serve as a central point to discuss implementation strategies to achieve the above goals.