What's the difference to RestWS? Why not join efforts?

Comments

senpai’s picture

Assigned: Unassigned » iamcarrico

Assigning to @ChinggizKhan for a response, but also want to point out that if a merger is desired by both parties, RestWS would need to be at a full, stable release well before DrupalCon Munich in order to be QA'ed and deployed on drupal.org.

Once entity_json goes live on drupal.org D7, there's not much point in "mergering" unless there's a very clear advantage in doing so. What I'm saying is, @fago and @ChinggizKhan need to hurry up and make a decision on this.

iamcarrico’s picture

So, originally @mirzu and I looked across D.o for other modules that could do this, and in our searches we never came up with another module. Clearly, we missed RestWS. Personally, I have no problem helping that module get to a full-stable release to be QA'd before Munich, and can take a look at it more closely this weekend.

Advantages

  • One less module doing similar things on D.o
  • Several heads are better than one
  • Although I havent fulled looked at the code, it seems to be simpler to pull any JSON object
  • Can be used for the whole of D.o to be accessed via JSON

Disadvantages

  • More hooks for Drupal to go through.
  • Will change the API previously used for project_issue drastically
  • Will require much more work to get this QA'd then Entity JSON (as this was for the most part just pulled out of project_issues)

Personally, I can help either way--- I think this is a question better suited for @dww, @senpai, or more of the D.o support team as they will really be the ones directly affected by the choice.

dww’s picture

Status: Active » Postponed

Cool, thanks. I just opened #1710850: Deploy RestWS for D7 project issue JSON to see if anyone else on the infra team cares, but I lean towards joining forces with RestWS and abandoning entity_json as the best long-term solution to this. Let's see what infra has to say and then we can move forward on merging/collaborating.

Thanks all,
-Derek

senpai’s picture

Status: Postponed » Active

Need this to stay active in the Entity JSON issue queue, since as of right now, entity_json is what's going to go live for the D7 Upgrade.

senpai’s picture

Assigned: iamcarrico » Unassigned
Status: Active » Postponed
Issue tags: +project, +drupal.org D7, +porting
patrickd’s picture

Status: Postponed » Active

Stable release of restws is now available,
reopening.

So what to do with this module? abandon?

http://drupal.org/node/1710850#comment-6354222

mitchell’s picture

I personally like this module's approach, so please don't abandon. RestWS is well-reviewed and stable, but this module's code is simpler and more understandable.

Edit: Moved relevant parts to #1710850-4: Deploy RestWS for D7 project issue JSON.

iamcarrico’s picture

Status: Active » Closed (fixed)

I am closing this issue, but leaving Entity JSON as a full project

Reasons:

  • RestWS has been selected for D.o usage
  • This module's simplicity is still desired
  • Any more issues can be brought up in the issue queue, like any other module