[
https://issues.apache.org/jira/browse/VYSPER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-64:
---
Attachment: VYSPER-64.1.patch
This patch is the first step (refactoring) towards towards persistence
[
https://issues.apache.org/jira/browse/VYSPER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-68:
---
Summary: Allow zero or more (instead of exactly one) 'item' element in a
publish message
Reporter: Michael Jakl
Assignee: Michael Jakl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-54:
---
Attachment: VYSPER-54.1.patch
Full patch against rev778637 (including patches from VYSPER-53
Error cases for Publish to a node
---
Key: VYSPER-71
URL: https://issues.apache.org/jira/browse/VYSPER-71
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
Assignee: Michael
[
https://issues.apache.org/jira/browse/VYSPER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714930#action_12714930
]
Michael Jakl edited comment on VYSPER-54 at 5/31/09 2:41 PM
[
https://issues.apache.org/jira/browse/VYSPER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-54:
---
Attachment: (was: VYSPER-54.1.patch)
Publish to a node (XEP-0060 7.1
[
https://issues.apache.org/jira/browse/VYSPER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-54:
---
Attachment: VYSPER-54.1.patch
Publish to a node (XEP-0060 7.1
Hi!
On Sun, May 31, 2009 at 23:40, Michael Jakl (JIRA) j...@apache.org wrote:
Michael Jakl updated VYSPER-54:
---
Attachment: VYSPER-54.1.patch
Full patch against rev778637 (including patches from VYSPER-53).
Bernd, for sending the event message to all
Error cases for Unsubscribe from a node
-
Key: VYSPER-67
URL: https://issues.apache.org/jira/browse/VYSPER-67
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
[
https://issues.apache.org/jira/browse/VYSPER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-53:
---
Attachment: VYSPER-53.1.patch
The basic unsubscribe use-case is covered with this patch. Error
[
https://issues.apache.org/jira/browse/VYSPER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-53:
---
Attachment: VYSPER-53.1.1.patch
This patch supersedes the VYSPER-53.1.patch and includes tests
[
https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12712012#action_12712012
]
Michael Jakl commented on VYSPER-52:
Thanks for the hint, I'll consider this when I
[
https://issues.apache.org/jira/browse/VYSPER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-64:
---
Description: Instead of instantiating the model whilst creating the
handlers, use storage providers
[
https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12712014#action_12712014
]
Michael Jakl commented on VYSPER-52:
You changed the order of the imports
Error cases for Subscribe to a node
-
Key: VYSPER-65
URL: https://issues.apache.org/jira/browse/VYSPER-65
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
Assignee
Hi!
On Fri, May 22, 2009 at 07:36, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
I've just uploaded a patch for some PubSub/Vysper feature. If I'd continue to
work on the sources wouldn't I come into troubles creating the next patch?
How
do you deal with such a situation
[
https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-52.
--
Resolution: Fixed
Patch applied. VYSPER-65 deals with the error cases.
Subscribe to a Node (XEP-0060
Unify error handling for pubsub
---
Key: VYSPER-63
URL: https://issues.apache.org/jira/browse/VYSPER-63
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
Assignee: Michael Jakl
[
https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-52:
---
Attachment: VYSPER-52.1.patch
VYSPER-52.1.patch adds the base usecase for subscribing to a node
Wire model classes to persitency providers
--
Key: VYSPER-64
URL: https://issues.apache.org/jira/browse/VYSPER-64
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
Hi!
I've just uploaded a patch for some PubSub/Vysper feature. If I'd continue to
work on the sources wouldn't I come into troubles creating the next patch? How
do you deal with such a situation?
Currently I just wait until the patch is applied and work on afterwards, but
that won't work well
Hi!
On Wed, May 20, 2009 at 07:25, Bernd Fondermann bf_...@brainlounge.de wrote:
From what I read in the spec so far this sounds good.
Maybe I'd not model the user roles as subclassas but as an enum type,
but this is already too implementation specific.
What also needed are some higher level
[
https://issues.apache.org/jira/browse/VYSPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-60.
Resolution: Fixed
Patch applied.
Reorganize handlers and testcases
Hi!
On Sun, May 17, 2009 at 00:44, Bernd Fondermann bf_...@brainlounge.de wrote:
I think it's time to plan and discuss about internal representation of
items and all the other data held within the pusub module. Do some
bottom up OO engineering. How that will be taken up by the handlers will
Hi!
On Sun, May 17, 2009 at 21:30, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
If you don't have too much pending work which is not stored anywhere
else, I recommend removing the bad dirs and then do svn update.
svn up (--force) didn't bring back my dirs. I had
Hi!
On Sat, May 16, 2009 at 22:44, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl (JIRA) wrote:
The patch corrects the disc#info integration of the pubsub module.
Applied.
For pubsub, more disco listeners are needed, right? Have you thought
about how to do this already?
No, I
Hi!
On Sat, May 16, 2009 at 22:52, Bernd Fondermann bf_...@brainlounge.de wrote:
For the pubsub module, I'd propose to
+ move the 'general' and 'owner' package to 'handler', or,
alternatively, move the handler classes they contain to two new
'handler' sub-packages respectively.
+1, I wasn't
Reorganize handlers and testcases
-
Key: VYSPER-60
URL: https://issues.apache.org/jira/browse/VYSPER-60
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
Assignee: Michael
[
https://issues.apache.org/jira/browse/VYSPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-60:
---
Attachment: VYSPER-60.1.patch
VYSPER-60.1
- Renames general to handler and owner to handler.owner
Hi!
On Sat, May 16, 2009 at 23:07, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
I can do it, if this proves to be too cumbersome to do in a patch.
Done already. But Eclipse (Subversion?) doesn't recognize renamings
and move operations so the patch is quite large :(
Cheers
Hi!
I've started with the disco(very) implementation yesterday. There seem
to be two possible ways of implementing disco, and the pubsub
extension at large.
The Pubsub Module is a subclass of DefaultDiscoAwareModule, which
provides three method-stubs to deal with disco:
-
Hi!
On Fri, May 15, 2009 at 14:26, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
The InfoRequest returns the disco information for a particular node.
The Pubsub module could be addressable by its own JID inside the
server. pubsub.vysper.org or something.
Not quite
[
https://issues.apache.org/jira/browse/VYSPER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-26.
--
Resolution: Fixed
All patches applied. Closed.
Implement Module-skeleton
Hi!
I've completed the handler skeletons for the XEP-0060 extension. For
now, we've got six handlers each assigned to one stanza type within
pubsub:
General namespace:
- subscribe
- unsubscribe
- publish
- create
Owner namespace:
- configure
- delete
In the following I'll try to explain a
Hi!
On Fri, Apr 24, 2009 at 22:49, Bernd Fondermann bf_...@brainlounge.de wrote:
Concerning tool support: that's a good point.
Creating something with smack.jar would be my first idea, if everything
else is not feasible.
smack got pubusb support:
[
https://issues.apache.org/jira/browse/VYSPER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-26:
---
Attachment: VYSPER-26.3.patch
This patch adds missing license declaration and author tags (existing
Hi!
On Tue, May 12, 2009 at 08:54, Bernd Fondermann bf_...@brainlounge.de wrote:
Emmanuel Lecharny wrote:
Note : We also have to use the same @author tags everywhere.
SSHd uses :
@author a href=mailto:dev@mina.apache.org;Apache MINA SSHD Project/a
FtpServer uses :
@author The Apache MINA
Hi!
On Tue, May 5, 2009 at 09:47, Julien Vermillard jvermill...@archean.fr wrote:
Le Tue, 28 Apr 2009 14:04:32 +0530,
Ashish paliwalash...@gmail.com a écrit :
On Tue, Apr 28, 2009 at 1:53 PM, Bernd Fondermann
Anyone from the experienced MINA crew who'd like to comment on
Hi!
On Wed, Apr 22, 2009 at 16:34, Bernd Fondermann bf_...@brainlounge.de wrote:
Vysper hit the main XMPP news today at
http://blog.xmpp.org/index.php/2009/04/xmpp-roundup-8/
A second mention:
http://blog.xmpp.org/index.php/2009/04/gsoc09-with-xmpp/
Unfortunately I called Vysper a
Hi!
On Sat, Apr 25, 2009 at 21:57, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
This might get interesting...
http://thetofu.com/archive/pubsublog_20090307.html
As well as this:
http://www.lobstermonster.org/post/xmpp-pubsub-service-to-publish-bbc-world-news
Cheers
Hi!
On Tue, Apr 28, 2009 at 10:54, Bernd Fondermann bf_...@brainlounge.de wrote:
@Michael: I've commented on one or two of your issues.
Thanks.
Is there a policy for JIRAs concerning closing/creating new ones?
Like VYSPER-26[1], should I close it and make a new one like this
Split existing
Hi!
On Thu, Apr 23, 2009 at 11:54, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
Until 2009-05-23 my plan would be to continue to explore the current Vysper
capabilities as well as to read the XEP-060 in detail.
Since this is also the Community Bonding Period, do you have
Hi!
On Sat, Apr 25, 2009 at 14:55, Ashish paliwalash...@gmail.com wrote:
We need means of creating, configuring, and deleting nodes (covers important
recommended features 8.1, 8.2, 8.4).
Where do you plan to store these *nodes*?
From implementation perspective, you need to be able to
Hi!
On Fri, Apr 24, 2009 at 13:29, Bernd Fondermann bf_...@brainlounge.de wrote:
The stanzas are now fetched from the direct-to-session queue, not from
the relaying queue.
Unit tests run through. Although I don't like the write(null) hack,
why not introduce a new method and call it reset()?
Hi!
On Fri, Apr 24, 2009 at 13:29, Bernd Fondermann bf_...@brainlounge.de wrote:
Please retry to run the unit tests.
The new statistics for the code coverage (or test coverage):
Exactly 70% of the server code gets executed when running all tests
(and 83.2% of the test-code is run).
Quite
Hi!
On Fri, Apr 24, 2009 at 16:25, Bernd Fondermann
bernd.fonderm...@googlemail.com wrote:
On Fri, Apr 24, 2009 at 15:15, Michael Jakl jakl.mich...@gmail.com wrote:
Exactly 70% of the server code gets executed when running all tests
(and 83.2% of the test-code is run).
Quite impressive
Hi!
To implement the XEP-060, I'd like to have a running example which would also
serve as a tool for evaluating the progress.
Here are my notes for it, please comment on it.
Bernd came up with something like Twitter. That would mean we have a node per
person (for example
Hi!
On Fri, Apr 24, 2009 at 22:49, Bernd Fondermann bf_...@brainlounge.de wrote:
Michael Jakl wrote:
Please be aware of XEP-0163 - Personal Eventing Protocol(*). Maybe you
want to check that we don't implement anything contradicting it.
(*) http://xmpp.org/extensions/xep-0163.html
Thanks
Hi!
On Wed, Apr 22, 2009 at 10:13, Bernd Fondermann bf_...@brainlounge.de wrote:
So, I propose to attach patches to JIRA (more than one patch per JIRA,
where appropriate) for the time being. At some point you may gain
committership (that's not my call, but the MINA PMCs, so I can be open
Hi!
On Wed, Apr 22, 2009 at 08:43, Ashish paliwalash...@gmail.com wrote:
Here is the code summary
Total files: 266
Total Size: 1.01MB
Total Lines: 25985 (100%)
Code Lines: 15133 (58.2%)
Comment Lines: 7616 (29.3%)
Blank Lines: 3383 (13.0%)
To add two more statistics (done with eclEMMA):
Good Morning!
On Tue, Apr 21, 2009 at 10:29, Bernd Fondermann bf_...@brainlounge.de wrote:
Congrats to Michael Jakl. :-)
Thank you and thanks to you ;)
He will be our MINA/Vysper Sommer of Code student for the next months[1].
Looking forward to your contributions, Michael,
Like the perfect
Hi!
On Tue, Apr 21, 2009 at 10:41, Ashish paliwalash...@gmail.com wrote:
Ps: Congrats to Ashish too :)
Which Ashish :-)
Isn't this your proposal?
http://socghop.appspot.com/student_project/show/google/gsoc2009/asf/t124021711323
Michael
Hello!
I'm reposting a slightly revised timetable how I plan to implement the XEP-060
(publish/subscribe) extension for Vysper.
Please comment on it.
Until 2009-05-23 my plan would be to continue to explore the current Vysper
capabilities as well as to read the XEP-060 in detail.
The pubsub
Hi!
Since I do not have committer access, how would you suggest to get the big
feature improvement into the code?
Currently I would make JIRA tasks (as soon as JIRA has moved) and upload
patches. This way Bernd can have a second look at the code.
I think the extension is mostly separate from
On Fri, Apr 17, 2009 at 15:48, Bernd Fondermann bf_...@brainlounge.de wrote:
concerning your contributions, could you please - if you don't mind - file a
ICLA with the ASF?
see http://www.apache.org/licenses/#clas
Done.
Cheers,
Michael
Hi!
On Sat, Apr 18, 2009 at 11:07, Emmanuel Lecharny elecha...@apache.org wrote:
May I suggest all those logo to be stored into the MINA logo page,
with a number, so when it will be a good timing for a vote, we can
simply point to this page ?
I would do so, but I don't have the right
Hi!
On Fri, Apr 17, 2009 at 08:37, Bernd Fondermann bf_...@brainlounge.de wrote:
Or We can have a logo which can depicts the XMPP theme
That was my first thought, too.
Maybe taking the XMPP logo[1] rainbows and make something feathery out of
them.
I've been playing around with the
Hi!
On Fri, Apr 17, 2009 at 11:04, Bernd Fondermann bf_...@brainlounge.de wrote:
I see what you mean by arranging the feathers like in the XMPP logo.
Can we make it more clear that this is intended to be a play on the XMPP
logo by chosing different colors or stylized feathers?
That's easier
Hi!
On Fri, Apr 17, 2009 at 13:15, Edouard De Oliveira doe_wan...@yahoo.fr wrote:
I like this one but i would make the feathers much smaller and place them on
the left so that they would be a little bit taller than the two lines figured
by the Vysper name and the mina logo.
\ /
\
On Fri, Apr 17, 2009 at 14:21, Edouard De Oliveira doe_wan...@yahoo.fr wrote:
i do agree if some remainder to mina is a wish maybe combining the V feathers
with mina logo (replacing the mina text with Vysper) is the way
Good point!
Here a few ideas based on the Mina logo:
On Fri, Apr 17, 2009 at 15:48, Bernd Fondermann bf_...@brainlounge.de wrote:
concerning your contributions, could you please - if you don't mind - file a
ICLA with the ASF?
see http://www.apache.org/licenses/#clas
Of course, I will do so on Monday.
Cheers,
Michael
201 - 262 of 262 matches
Mail list logo
