Hi Andy, I took a look at the Jira list and found some other items that might be good places to start
* ESME-25 Ability to set proxy user and proxy password from property file * ESME-72 Add other attributes to the AccessPool object * ESME-26 The message parser should ignore # in urls D. On Thu, Jul 2, 2009 at 6:01 AM, Richard Hirsch<[email protected]> wrote: > The JMX interface sounds like a good place to start and will give you > a chance to play with the code. It also something which is important > for success in the Enterprise arena. Once we have an initial version > of the code deployed on stax (in the cloud), I'll try and use an > off-the-shelf tool to access it. > > I like your suggestions as well about possible stats. > > Sorry about the vague JIRA items, I'll work on that. > > If you want I could add an JIRA item to finish the java wrapper for > the REST-API which is still unfinished. This would also give you a > chance to test ESME's functionality and get familiar with it. While > you are working on that we will work on making the Scala-based JIRA > items more concrete. > > Thanks for getting involved. > > D. > > ue Jira On Thu, Jul 2, 2009 at 2:29 AM, Andy the > destroyer<[email protected]> wrote: >> Darren, >> >> I have built the code from the trunk from subversion and got it running ( >> for the most part; getting a bunch of js exceptions). Anyways, I went >> through the unassigned tasks on JIRA and found that most of them were vague >> suggestions and did not give a clear starting point. That said I have worked >> with JMX a good amount and could add a statistics MBean. What sort of stats >> would your want. I was thinking.. >> >> Attributes >> # messages sent >> # groups >> uptime >> # messages sent last X minutes ( or other metric for general load ) >> # users total >> # users logged in >> >> Operations >> # messages sent by group / tag etc. >> # messages sent my user >> # follows by user >> reset >> >> What do you think. could also work on code documentation. I did notice an >> unassigned ticket for that however usually need to work with the code for a >> while to understand it in order to document it correctly. >> >> -Andy >> >> On Wed, Jul 1, 2009 at 2:20 PM, Andy the destroyer < >> [email protected]> wrote: >> >>> Hi Darren, >>> >>> I will have a go at it this weekend. Thanks for the response everyone. >>> >>> -Andy >>> >>> >>> On Wed, Jul 1, 2009 at 2:10 PM, Darren Hague <[email protected]>wrote: >>> >>>> Hi Andrew, >>>> >>>> Check out the source code, try building it, then have a look at the wiki >>>> and the list of JIRA tickets. Find a JIRA you're comfortable in having a go >>>> at, ask here if you have any questions or need any help, then submit a >>>> patch >>>> with your code. >>>> >>>> After a few patches (if you stick around that long ;-), we'll likely have >>>> a vote and formally >>>> welcome you as a committer to the project. >>>> >>>> Welcome aboard! >>>> >>>> All the best, >>>> Darren >>>> >>>> >>>> Andy the destroyer wrote: >>>> >>>>> Hello, >>>>> >>>>> My name is Andrew Headrick. I am an experienced Java developer and am >>>>> learning Scala but have no professional experience with it yet. I would >>>>> like >>>>> to contribute to this project in anyway I can that involves code so I may >>>>> gain more experience and help the community. I can give references if >>>>> they >>>>> are needed and a detailed list of technologies and languages I have >>>>> worked >>>>> with. >>>>> >>>>> Regards, >>>>> Andrew Headrick >>>>> [email protected] >>>>> >>>>> >>>>> >>>> >>>> >>> >> >
