I have worked lately on morbid (the STOMP server that starts if you
specify a stomp://:61613 line in your orbited config file).
The result is in a public repository so that anyone can look at it:
http://bitbucket.org/faide/morbid
I have done some additions like the receipt header support and support
for transactions. And added some unit tests to cover my changes and
ensure I would not break anything in the process.
To be on the safe side I also tested the STOMP demo provided by
orbited and it worked (transactions included).
I am interested to hear about problems/successes you may encounter
while trying to use my version with (or without) orbited.
Cheers,
Florent
Yep :)
I would be interested to see my changes go into the main morbid
development tree. Looking at the morbid page on pypi it appears that
no release was issued since two years... Who's maintaining morbid at
the moment?
I have read on Michael Carter's orbited2 project that he gave the
orbited project to some other maintainer and that in orbited2 he did
not intend to
implement/use morbidq at all.
Cheers,
Florent
> Regards,
> Niklas
>
> On Aug 12, 11:00 pm, Florent Aide <florent.a...@gmail.com> wrote:
>> Hello all,
>>
>> I have worked lately on morbid (the STOMP server that starts if you
>> specify a stomp://:61613 line in your orbited config file).
>> The result is in a public repository so that anyone can look at it:
>>
>> http://bitbucket.org/faide/morbid
>>
[...]
[...]
> It's probably best to create a new github repo with your (updated)
> code and then hope we can add it as official (pypi) when we can get
> ahold of mcarter. You can probably see if you can take over the morbid
> repo on pypi, I would suggest signing up and contacting pypi (then
> must have routines for these matters).
Hi Niklas,
pypi seems ok "on the principle" to give control of the package page
if I first do some beta cycle. So I'll just announce a beta release
here in a few minutes.
Here is the ticket I file to pypi:
http://sourceforge.net/tracker/?func=detail&atid=513503&aid=3394753&group_id=66150
You can find the discussion in the comments section at the end (by
expending them first).
Cheers,
Florent