Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 8:14 AM, Ashish paliwalash...@gmail.com wrote: Was just thinking, will it be worth releasing Vysper once we have MINA 2.0 GA? Its closeby and if we can get Vysper running with MINA RC, it would be just a verification of release :) I do not see any immediate reason for Vysper to wait for MINA GA, the Vysper release will be an early preview anyways. But, I agree that having Vysper on MINA 2.0 RC would be a good verification of MINA. /niklas
Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 2:01 PM, Niklas Gustavsson nik...@protocol7.com wrote: On Mon, Mar 8, 2010 at 8:14 AM, Ashish paliwalash...@gmail.com wrote: Was just thinking, will it be worth releasing Vysper once we have MINA 2.0 GA? Its closeby and if we can get Vysper running with MINA RC, it would be just a verification of release :) I do not see any immediate reason for Vysper to wait for MINA GA, the Vysper release will be an early preview anyways. But, I agree that having Vysper on MINA 2.0 RC would be a good verification of MINA. ok.. When are we planning a Vysper release? -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 9:38 AM, Ashish paliwalash...@gmail.com wrote: ok.. When are we planning a Vysper release? Given the current discussion on the other thread, I think we could start a vote any day now. /niklas
Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 2:16 PM, Niklas Gustavsson nik...@protocol7.com wrote: On Mon, Mar 8, 2010 at 9:38 AM, Ashish paliwalash...@gmail.com wrote: ok.. When are we planning a Vysper release? Given the current discussion on the other thread, I think we could start a vote any day now. :) Great ! I am just worried about the documentation part.. I guess we are nowhere :( we would atleast need something to get the users started. -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 9:51 AM, Ashish paliwalash...@gmail.com wrote: I am just worried about the documentation part.. I guess we are nowhere :( we would atleast need something to get the users started. Agreed. At minimum, I think we need a Getting started tutorial. /niklas
Re: Vysper release?
On Sun, Mar 7, 2010 at 11:29 PM, Bernd Fondermann bf_...@brainlounge.de wrote: I think, a 0.5 release number would sound right. I have no really opinion on the version numbering besides noting that we've used milestones (1.0-M1, 1.0-M2...) for MINA and FtpServer. And I'd like to get the website ready beforehand. Agreed, a basic website needs to be in place. /niklas
[vysper] waiting for the protocolworker to complete
Hi all, I don't know if my question yesterday was concrete enough. I try to send an unavailable message when the connection breaks down and I wonder if I can somehow wait for the message to go out. Because afterwards the session gets CLOSED and an unbind happens, which now makes my attempt to send the unavailable break. Or is there a way to send a Stanza synchronuosly? Any help would be appreciated, 'cause I truly need this. Regards Thomas
Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 09:57, Niklas Gustavsson nik...@protocol7.com wrote: On Mon, Mar 8, 2010 at 9:51 AM, Ashish paliwalash...@gmail.com wrote: I am just worried about the documentation part.. I guess we are nowhere :( we would atleast need something to get the users started. Agreed. At minimum, I think we need a Getting started tutorial. +1. There is still content left at Lab's cwiki. I'll take the task of adding some doc. Bernd
Re: Vysper release?
On Mon, Mar 8, 2010 at 10:06, Niklas Gustavsson nik...@protocol7.com wrote: On Sun, Mar 7, 2010 at 11:29 PM, Bernd Fondermann bf_...@brainlounge.de wrote: I think, a 0.5 release number would sound right. I have no really opinion on the version numbering besides noting that we've used milestones (1.0-M1, 1.0-M2...) for MINA and FtpServer. Of course we could align this with MINA best practice. However, I think a 1.0-XXX notation would be a little bit misleading feature-completelyness-wise. Bernd
Re: [Vysper] Porting to MINA 2.0 M5
On Mon, Mar 8, 2010 at 3:05 PM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Mon, Mar 8, 2010 at 09:57, Niklas Gustavsson nik...@protocol7.com wrote: On Mon, Mar 8, 2010 at 9:51 AM, Ashish paliwalash...@gmail.com wrote: I am just worried about the documentation part.. I guess we are nowhere :( we would atleast need something to get the users started. Agreed. At minimum, I think we need a Getting started tutorial. +1. There is still content left at Lab's cwiki. I'll take the task of adding some doc. i think we migrated all the stuff. I am not really very sure.. lets confirm once more, I am getting old :( We can hijack the MINA2 wiki design.. choose a color and get going..
Re: Vysper release?
On Mon, Mar 8, 2010 at 3:11 PM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Mon, Mar 8, 2010 at 10:06, Niklas Gustavsson nik...@protocol7.com wrote: On Sun, Mar 7, 2010 at 11:29 PM, Bernd Fondermann bf_...@brainlounge.de wrote: I think, a 0.5 release number would sound right. I have no really opinion on the version numbering besides noting that we've used milestones (1.0-M1, 1.0-M2...) for MINA and FtpServer. Of course we could align this with MINA best practice. However, I think a 1.0-XXX notation would be a little bit misleading feature-completelyness-wise. How about starting with 0.1 release and them pumping up the versions? -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Release FtpServer 1.0.4 - take 2
On Mon, Mar 8, 2010 at 10:35 AM, Dave Roberts dave.robe...@saaconsultants.com wrote: Obviously I'm a little biased, but I would have liked to have seen issue FTPSERVER-344 resolved before the release. I think this patch is a bit to complex to motivate including it into a bug fix release. Therefore I would like to see it in 1.1.0. And that we focus on getting 1.1.0 out fairly soon. /niklas
Editing cwiki
Hi, Please help me how I would create proper cwiki content for Vysper. Should I start from http://mina.apache.org/vysper or http://mina.apache.org/mina2/vysper/ Cheers, Bernd
Re: [VOTE] Release FtpServer 1.0.4 - take 2
On 08/03/2010 10:17, Niklas Gustavsson wrote: On Mon, Mar 8, 2010 at 10:35 AM, Dave Roberts dave.robe...@saaconsultants.com wrote: Obviously I'm a little biased, but I would have liked to have seen issue FTPSERVER-344 resolved before the release. I think this patch is a bit to complex to motivate including it into a bug fix release. Therefore I would like to see it in 1.1.0. And that we focus on getting 1.1.0 out fairly soon. Good point Niklas, that makes a lot more sense.
Re: Editing cwiki
On Mon, Mar 8, 2010 at 11:25 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: Should I start from http://mina.apache.org/vysper or http://mina.apache.org/mina2/vysper/ It's all a matter of how we sync the exported content from Confluence to the web site, not so much how we edit it. So, for now I think we should edit the wiki at http://cwiki.apache.org/confluence/display/VYSPER. And that will then be synced to http://mina.apache.org/vysper/ (every hour or so). /niklas
[jira] Commented: (FTPSERVER-349) WhiteList
[ https://issues.apache.org/jira/browse/FTPSERVER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842621#action_12842621 ] David Latorre commented on FTPSERVER-349: - Hello Devnull, When i first revised your patch I noticed this problem. I considered some possibilities you haven't mentioned: -1. In the method that adds the subnets/ips to the WhiteListFilter ( updateWhitelistFilter(), right?) we can remove the filter from the chain if we have an empty subnet list. This would work but I'm concerned that ftpserver users may want to use WhiteListFilter when it is not in the chain. -2. Explictly check for the address 0.0.0.0/0 and consider it to mean all addresses allowed. If we move the WhiteListFilter to MINA-core, it might be worth discussing there how to signal that all addresses are allowed. What do you think, Niklas? WhiteList - Key: FTPSERVER-349 URL: https://issues.apache.org/jira/browse/FTPSERVER-349 Project: FtpServer Issue Type: Improvement Components: Server Affects Versions: 1.0.3 Reporter: DevNull43 Priority: Trivial Fix For: 1.1.0 Attachments: WhiteList.txt WhiteList filer Restricting access to FTP based on a WhiteList BlackList - Allow all, Deny some. WhiteList - Deny all, Allow some. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release FtpServer 1.0.4 - take 2
Le Sun, 7 Mar 2010 21:23:41 +0100, Niklas Gustavsson nik...@protocol7.com a écrit : Hey, Alright, I've fixed the issues found by Sai, here's take 2 on this release vote. You can find the distributions and Maven artifacts here: http://people.apache.org/~ngn/ftpserver/1.0.4/ These files was built from the following code: https://svn.apache.org/repos/asf/mina/ftpserver/branches/1.0.4 Changelog: https://issues.apache.org/jira/browse/FTPSERVER/fixforversion/12314283 [ ]: +1, Release FtpServer 1.0.4 [ ]: 0, Abstain [ ]: -1, Don't release FtpServer 1.0.4 /niklas Just a question, what is the pom.xml-e is the source tarball ? -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Re: Editing cwiki
On Mon, Mar 8, 2010 at 4:01 PM, Niklas Gustavsson nik...@protocol7.com wrote: On Mon, Mar 8, 2010 at 11:25 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: Should I start from http://mina.apache.org/vysper or http://mina.apache.org/mina2/vysper/ It's all a matter of how we sync the exported content from Confluence to the web site, not so much how we edit it. So, for now I think we should edit the wiki at http://cwiki.apache.org/confluence/display/VYSPER. And that will then be synced to http://mina.apache.org/vysper/ (every hour or so). I took a quick look at the wiki. Most of the lab pages are there, but Getting Started needs to be improved. Navigation needs to be build :( I did a bad job there.. It seems there is a significant work need to come close to a usable documentation. We need atleast 3 things. Getting Started Dev Guide Downloads not to mention, folks we need to finalize on the logo as well.. -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: Editing cwiki
On Mon, Mar 8, 2010 at 11:45 AM, Ashish paliwalash...@gmail.com wrote: Getting Started Dev Guide Downloads We should also have a Mailing lists page, we can probably steal that right away from MINA or FtpServer. /niklas
Re: Editing cwiki
On Mon, Mar 8, 2010 at 4:27 PM, Niklas Gustavsson nik...@protocol7.com wrote: On Mon, Mar 8, 2010 at 11:45 AM, Ashish paliwalash...@gmail.com wrote: Getting Started Dev Guide Downloads We should also have a Mailing lists page, we can probably steal that right away from MINA or FtpServer. +1 lets reuse :) -- thanks ashish
Re: [VOTE] Release FtpServer 1.0.4 - take 2
Le Mon, 8 Mar 2010 11:54:32 +0100, Niklas Gustavsson nik...@protocol7.com a écrit : On Mon, Mar 8, 2010 at 11:40 AM, Julien Vermillard jvermill...@archean.fr wrote: Just a question, what is the pom.xml-e is the source tarball ? It's a plain mistake from my end (a script I used during the release process blew up and generated a pom.xml-e in each module. I removed these but obviously missed the one in the root of the project). I'll push out new zip/tar files without this file. /niklas Can I beg for tar.bz2 too ? :) -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Re: [VOTE] Release FtpServer 1.0.4 - take 2
+1 Let's go for it! Regards, Sai Pullabhotla On Sun, Mar 7, 2010 at 2:23 PM, Niklas Gustavsson nik...@protocol7.com wrote: Hey, Alright, I've fixed the issues found by Sai, here's take 2 on this release vote. You can find the distributions and Maven artifacts here: http://people.apache.org/~ngn/ftpserver/1.0.4/ These files was built from the following code: https://svn.apache.org/repos/asf/mina/ftpserver/branches/1.0.4 Changelog: https://issues.apache.org/jira/browse/FTPSERVER/fixforversion/12314283 [ ]: +1, Release FtpServer 1.0.4 [ ]: 0, Abstain [ ]: -1, Don't release FtpServer 1.0.4 /niklas
Re: [jira] Commented: (FTPSERVER-349) WhiteList
On Mon, Mar 8, 2010 at 2:27 PM, Sai Pullabhotla sai.pullabho...@jmethods.com wrote: Why not have asterisk(s) represent allow all? I think we should stick to using CIDR notation. 0.0.0.0/0 should work, if it doesn't that's a bug in our current implementation and needs fixing. For my 2 cents, I think a white list filter should work as: * If the list of subnets is empty: allow all IP addresses * As soon as a subnet/IP address is added, only allow for that This would save our users from having to keep track of the state of the filter themselves (and move it in or out ióf the filter chain). /niklas
[jira] Created: (VYSPER-185) Send unavailable on lost connection
Send unavailable on lost connection --- Key: VYSPER-185 URL: https://issues.apache.org/jira/browse/VYSPER-185 Project: VYSPER Issue Type: Bug Components: core protocol Reporter: Thomas Kratz Priority: Minor If the clients drops the connection or connection gets broken, an anavailable should be sent out to other parties. I need this fix, because I manage license based on the presence of users and if a client breaks down (yes it does sometimes, its eclipse based) I need to release the license. I'll attach a pacth for this (is state of my work) and kindly ask you to have a look at it. It currently breaks testProcessUnknownStanza(org.apache.vysper.xmpp.protocol.ProtocolWorkerProcess TestCase) and I don't have deep enough understanding why this happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (VYSPER-185) Send unavailable on lost connection
[ https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Kratz updated VYSPER-185: Attachment: AbstractSessionContext.java.patch Excuse the ill formatting, dont know your settings for that. Send unavailable on lost connection --- Key: VYSPER-185 URL: https://issues.apache.org/jira/browse/VYSPER-185 Project: VYSPER Issue Type: Bug Components: core protocol Reporter: Thomas Kratz Priority: Minor Attachments: AbstractSessionContext.java.patch If the clients drops the connection or connection gets broken, an anavailable should be sent out to other parties. I need this fix, because I manage license based on the presence of users and if a client breaks down (yes it does sometimes, its eclipse based) I need to release the license. I'll attach a pacth for this (is state of my work) and kindly ask you to have a look at it. It currently breaks testProcessUnknownStanza(org.apache.vysper.xmpp.protocol.ProtocolWorkerProcess TestCase) and I don't have deep enough understanding why this happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release FtpServer 1.0.4 - take 2
Le Mon, 8 Mar 2010 15:17:24 +0100, Niklas Gustavsson nik...@protocol7.com a écrit : On Mon, Mar 8, 2010 at 2:02 PM, Julien Vermillard jvermill...@archean.fr wrote: Can I beg for tar.bz2 too ? :) I'll add a JIRA issue for doing this for 1.0.5 if that's okay with you? /niklas Yep, it's not really important. -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
[jira] Assigned: (VYSPER-185) Send unavailable on lost connection
[ https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-185: --- Assignee: Bernd Fondermann Send unavailable on lost connection --- Key: VYSPER-185 URL: https://issues.apache.org/jira/browse/VYSPER-185 Project: VYSPER Issue Type: Bug Components: core protocol Reporter: Thomas Kratz Assignee: Bernd Fondermann Priority: Minor Attachments: AbstractSessionContext.java.patch, VYSPER-185.2.patch If the clients drops the connection or connection gets broken, an anavailable should be sent out to other parties. I need this fix, because I manage license based on the presence of users and if a client breaks down (yes it does sometimes, its eclipse based) I need to release the license. I'll attach a pacth for this (is state of my work) and kindly ask you to have a look at it. It currently breaks testProcessUnknownStanza(org.apache.vysper.xmpp.protocol.ProtocolWorkerProcess TestCase) and I don't have deep enough understanding why this happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (VYSPER-185) Send unavailable on lost connection
[ https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-185: Attachment: VYSPER-185.2.patch Please see if this patch is behaving more correctly for your use case. Additionally, please note that this is not a sufficient committable patch because: + patch is largely untested + endSession() is called not only on session abortion, but also in other cases, where sending unavail to the session client is not allowed + we should not send unavail to the initiating entity, only to contacts + when we are not in session abortion case, we should send /stream:stream Send unavailable on lost connection --- Key: VYSPER-185 URL: https://issues.apache.org/jira/browse/VYSPER-185 Project: VYSPER Issue Type: Bug Components: core protocol Reporter: Thomas Kratz Priority: Minor Attachments: AbstractSessionContext.java.patch, VYSPER-185.2.patch If the clients drops the connection or connection gets broken, an anavailable should be sent out to other parties. I need this fix, because I manage license based on the presence of users and if a client breaks down (yes it does sometimes, its eclipse based) I need to release the license. I'll attach a pacth for this (is state of my work) and kindly ask you to have a look at it. It currently breaks testProcessUnknownStanza(org.apache.vysper.xmpp.protocol.ProtocolWorkerProcess TestCase) and I don't have deep enough understanding why this happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (FTPSERVER-349) WhiteList
Is there a way to have these emails added to the JIRA discussion? I just created a ticket in MINA filter for this 0.0.0.0/0 feature. 2010/3/8 Niklas Gustavsson nik...@protocol7.com: On Mon, Mar 8, 2010 at 2:27 PM, Sai Pullabhotla sai.pullabho...@jmethods.com wrote: Why not have asterisk(s) represent allow all? I think we should stick to using CIDR notation. 0.0.0.0/0 should work, if it doesn't that's a bug in our current implementation and needs fixing. For my 2 cents, I think a white list filter should work as: * If the list of subnets is empty: allow all IP addresses * As soon as a subnet/IP address is added, only allow for that This would save our users from having to keep track of the state of the filter themselves (and move it in or out ióf the filter chain). /niklas
[jira] Created: (DIRMINA-773) org.apache.mina.filter.firewall.Subnet should consider 0.0.0.0/0 as a subnet that contains 'all the ipv4 addresses'
org.apache.mina.filter.firewall.Subnet should consider 0.0.0.0/0 as a subnet that contains 'all the ipv4 addresses' Key: DIRMINA-773 URL: https://issues.apache.org/jira/browse/DIRMINA-773 Project: MINA Issue Type: Improvement Components: Filter Affects Versions: 2.0.0-RC1 Reporter: David Latorre One of our users when trying to implement a WhilteListFilter found the problem that there is no way to declare a subnet that would comprise any ip address. As discussed in dev-mailing list, a 0.0.0.0/0 subnet should return always true for Subnet.inSubnet( any_ipv4_address) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (FTPSERVER-349) WhiteList
On Mon, Mar 8, 2010 at 6:41 PM, David Latorre dvl...@gmail.com wrote: Is there a way to have these emails added to the JIRA discussion? I just created a ticket in MINA filter for this 0.0.0.0/0 feature. Add a link to the mailing list archive to this thread. /niklas
[jira] Created: (FTPSERVER-354) Include tar.bz2 distribution
Include tar.bz2 distribution Key: FTPSERVER-354 URL: https://issues.apache.org/jira/browse/FTPSERVER-354 Project: FtpServer Issue Type: Improvement Reporter: Niklas Gustavsson Assignee: Niklas Gustavsson Fix For: 1.0.5, 1.1.0 Include a tar.bz2 compressed distribution package. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [vysper] waiting for the protocolworker to complete
Thomas Kratz wrote: Hi all, I don't know if my question yesterday was concrete enough. I try to send an unavailable message when the connection breaks down and I wonder if I can somehow wait for the message to go out. Wait a second. There are different cases: a. Client sends pres unavail.../ and keeps connection alive b. Client sends pres unavail.../ (maybe followed by a /stream:stream and closes the socket c. Client dies, Routing is broken, Socket cannot transport packets successfully end-to-end and the server detects this, because the socket gets closed - this is without the client notifying the server of anything d. Server goes down and is in process of ending all sessions Up until now, I thought we were talking c., right? a. is (should be) already working b. is not fully working, but we would be working on the wrong end then d. must be handled completely different. So, what is/are your case(s)? Because afterwards the session gets CLOSED and an unbind happens, which now makes my attempt to send the unavailable break. Or is there a way to send a Stanza synchronuosly? in MinaBackedSessionContext there is write(Stanza). This is a hack. So is everything attached to VYSPER-185. Bernd
Re: [VOTE] Release FtpServer 1.0.4 - take 2
[X]: +1, Release FtpServer 1.0.4 -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: Vysper release?
On 3/7/10 9:24 PM, Niklas Gustavsson wrote: Hi How about making a first release of Vysper? I think got more than enough functionality for a first milestone. /niklas Yeah, that would help the project to gain visibility. -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: Vysper release?
Emmanuel Lecharny wrote: On 3/7/10 9:24 PM, Niklas Gustavsson wrote: Hi How about making a first release of Vysper? I think got more than enough functionality for a first milestone. /niklas Yeah, that would help the project to gain visibility. That will be great. I've started to experiment with XMPP in the Apache Tuscany project and Vysper is working well for me. It'll be useful to get a release! -- Jean-Sebastien
Re: [VOTE] Release FtpServer 1.0.4 - take 2
Le Mon, 8 Mar 2010 15:54:41 +0100, Julien Vermillard jvermill...@archean.fr a écrit : Le Mon, 8 Mar 2010 15:17:24 +0100, Niklas Gustavsson nik...@protocol7.com a écrit : On Mon, Mar 8, 2010 at 2:02 PM, Julien Vermillard jvermill...@archean.fr wrote: Can I beg for tar.bz2 too ? :) I'll add a JIRA issue for doing this for 1.0.5 if that's okay with you? /niklas Yep, it's not really important. Sources and Tarballs looks fine : +1 -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Re: [VOTE] Release FtpServer 1.0.4 - take 2
On Tue, Mar 9, 2010 at 7:58 AM, Julien Vermillard jvermill...@archean.fr wrote: Sources and Tarballs looks fine : I should note that I updated the source distributions to not include the pom.xml-e that I added by mistake. It was the only change made, no change in SVN was needed as the file only existed in my local repo. /niklas
