Opened 15 years ago

Last modified 10 years ago

#1960 enhancement new

AMP implementation: Java

Reported by: Glyph Owned by: Allister MacLeod
Priority: low Milestone:
Component: core Keywords:
Cc: Gregory Armer, Jean-Paul Calderone, Allister MacLeod Branch:


Change History (12)

comment:1 Changed 15 years ago by Glyph

Status: newassigned

For kind of weird reasons, I've actually started working on this. There are a bunch of difficult design decisions, mostly centering around the fact that aside from EIO, there doesn't appear to be a good analogue of Twisted for Java, so doing everything event-driven is possible to code and test, but kind of difficult to actually run.

comment:2 Changed 14 years ago by Glyph

There's an implementation of this in a branch, java-1960, but I'm developing this in a separate repository to try to get some folks I know who know Java to contribute to it. When it's in a more suitable state for including in Twisted I'll put it into a newer branch.

comment:3 Changed 14 years ago by Glyph

Priority: lowlowest
Status: assignednew

If anyone is looking for this, I've moved it to a personal repository on Launchpad:

Eventually, maybe this will be in Twisted, but I think that perhaps external AMP implementations should just be external.

comment:4 Changed 14 years ago by Jean-Paul Calderone

Priority: lowestnormal

I suggest updating AMP documentation (module docstring, wiki page, something) with a link to the external implementations and then closing tickets such as this one, rather than leaving them open at lowest priority for the next fifty years.

comment:5 Changed 13 years ago by Gregory Armer

Cc: Gregory Armer added

comment:6 in reply to:  4 Changed 13 years ago by Glyph

Replying to exarkun:

I suggest updating AMP documentation (module docstring, wiki page, something) with a link to the external implementations

I am basically in agreement, with a few qualifications. I guess that would make me "+0.5" on this?

The only reason it's still open right now is that there aren't really any other maintained implementations. I've got a prototype in Java, Elisp, and there's the thing in the sandbox for PHP, but none of those have the project infrastructure that Twisted does (buildbots, ticket trackers, etc). None of them even have a web page explaining what it is.

I'd like to avoid closing this ticket until there's at least a single web page and feedback channel for the referenced protocol implementation for the aforementioned wiki page to link to. It doesn't have to be integrated with Twisted's existing infrastructure, although that would be a nice bonus.

comment:7 Changed 12 years ago by Glyph

Priority: normallow

I'm still going to let this hang out at low priority while I wait for someone to come along and maintain the Java code. Maybe one day I will.

comment:8 Changed 12 years ago by Jean-Paul Calderone

Cc: Jean-Paul Calderone added

So the resolution for this ticket is "maintain the Java code at"? What maintenance does it need? Please be specific. :)

comment:9 Changed 12 years ago by Glyph

It needs someone who cares enough to actually use it. Here are a few things I think it needs before anyone could use it without reading and understanding all of the code themselves:

  1. some actual releases of the code
  2. a project on launchpad instead of a pile of code in a repository somewhere
  3. a separate repository, just including the Java code
  4. more test coverage (there are a few things that are missing)
  5. more doc coverage, including an introductory document on how to use it

comment:10 Changed 11 years ago by <automation>

Owner: Glyph deleted

comment:11 Changed 10 years ago by Allister MacLeod

Cc: Allister MacLeod added

comment:12 Changed 10 years ago by Glyph

Owner: set to Allister MacLeod

Oh look, interest. (Please see the AMP protocol site's implementations page and let teratorn know if you'd like to maintain it.)

Note: See TracTickets for help on using tickets.