Hi!
On Wed, Oct 14, 2009 at 16:22, Fernando Padilla wrote:
> I am interested in moving Vysper forward, and part of that feature set (
> BOSH support ), I would like to have an async-http library to work off of.
> I do see Asyncweb linked to from the Mina homepage, but I can't find any
> releases
Hi!
On Tue, Sep 1, 2009 at 11:27, Bernd Fondermann wrote:
> It's not 'easier'. It would use less objects, yet not neccessarily much
> less memory though. Think about it: Queueing up the character data needs
> much more memory: what's now stored as 1 immutable inner object (and
> it's children) is
Hi!
On Tue, Sep 1, 2009 at 10:45, Bernd Fondermann wrote:
> Michael Jakl wrote:
>> On Mon, Aug 31, 2009 at 19:40,
>> bernd.fondermann wrote:
>>> If you want to relay a message to many addressees (say thousands), we
>>> might not want to create 1000 lists, if
Hi!
On Mon, Aug 31, 2009 at 19:40,
bernd.fondermann wrote:
> If you want to relay a message to many addressees (say thousands), we
> might not want to create 1000 lists, if we only want to replace the from
> entity for every new stanza and could reuse one list for that for every
> call of StanzaBu
Hi!
On Mon, Aug 31, 2009 at 10:16, Julien Vermillard wrote:
> I think this URL is a good start :
> http://hudson.zones.apache.org/hudson/view/Vysper/
Thanks.
This are the last words of our run (after a 60 hour run). I'm not sure
if the lines are related to the behavior, but our logging doesn't h
Hi!
On Mon, Aug 31, 2009 at 07:28, Bernd Fondermann wrote:
> Anybody knows what to do?
Is there a way to find how how Vysper was run, and eventually get the logs?
Michael
> Original Message
> Subject: I've disabled a vysper job on hudson
> Date: Sun, 30 Aug 2009 17:51:52 -0400
Hi!
On Tue, Aug 25, 2009 at 15:24, Niklas Gustavsson wrote:
> If the client send a full JID, that is true. But, as in the case of
> Smack, the client might not send a "from" attribute at all, in which
> case we will need to figure out a resource anyways (not sure yet what
> the best way is or if t
[
https://issues.apache.org/jira/browse/VYSPER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-151.
-
Resolution: Fixed
> Fix and extend "affi
[
https://issues.apache.org/jira/browse/VYSPER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-160.
-
Resolution: Fixed
> Enable transitions between affiliations (owner-t
[
https://issues.apache.org/jira/browse/VYSPER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-161.
-
Resolution: Fixed
> Make sure that the last "owner"
[
https://issues.apache.org/jira/browse/VYSPER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-159:
Parent Issue: VYSPER-152 (was: VYSPER-151)
> Introduce the subscription states (none, pend
[
https://issues.apache.org/jira/browse/VYSPER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-178.
-
Resolution: Fixed
> Implement Retrieve Affiliations (8.
[
https://issues.apache.org/jira/browse/VYSPER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-178:
Component/s: XEP0060 PubSub
> Implement Retrieve Affiliations (8.
Implement Retrieve Affiliations (8.9.1)
---
Key: VYSPER-178
URL: https://issues.apache.org/jira/browse/VYSPER-178
Project: VYSPER
Issue Type: Sub-task
Reporter: Michael Jakl
Hi!
On Fri, Aug 21, 2009 at 12:09, Ashish wrote:
> Had updated the Main documentation page to add Codec Repo link, couple
> of days back.
> Well as of now the page is not displaying as a table, as it used to be.
>
> Have tried everything I knew to make it look better, but it seems it
> won't liste
Hi!
On Tue, Aug 18, 2009 at 07:46, Bernd Fondermann wrote:
> At first: Congratulations for successfully completing your GSoC09
> project on time! It's been a pleasure for me to see you working on PubSub.
Thank you, it was a pleasure for me too!
> I hope we see you working on Vysper in future.
O
[
https://issues.apache.org/jira/browse/VYSPER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-171.
---
> Retrieve Affiliations (XEP-0060 5.7)
>
>
>
[
https://issues.apache.org/jira/browse/VYSPER-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-90.
--
> Make sure that a publisher can only overwrite items published by him/
[
https://issues.apache.org/jira/browse/VYSPER-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-88.
--
> disco#info for LeafNodes is incomplete.
> ---
>
>
[
https://issues.apache.org/jira/browse/VYSPER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-158.
---
> Introduce the various affiliations a user can h
[
https://issues.apache.org/jira/browse/VYSPER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-149.
---
> Pubsub Handlers hold state
> --
>
> Key
[
https://issues.apache.org/jira/browse/VYSPER-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-55.
--
> Create a Node (XEP-0060 8.1)
>
>
> Ke
[
https://issues.apache.org/jira/browse/VYSPER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-85.
--
> Retrieve subscriptions for LeafNodes (XEP-0060
[
https://issues.apache.org/jira/browse/VYSPER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-51.
--
> Discovery for Leaf Nodes (XEP-0060 5.3)
> ---
>
>
[
https://issues.apache.org/jira/browse/VYSPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-86.
--
> Order the items of a node (messages) in reversed chronological order when
> requesting all/some
[
https://issues.apache.org/jira/browse/VYSPER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-64.
--
> Wire model classes to storage providers
> ---
>
>
Hi!
2009/8/15 Martin Zruban :
> I recently came across the Vysper project and I was thinking about
> implementing a gateway for other IM protocols. To be precise, I thought
> about implementing it as the XEP-0100 extension [1] and I considered
> inspiring myself with Kraken IM plugin for Openfire
Hi!
I've added a few introductory lines on our Wiki. It can be found
here[1]. I thought I was editing the page on
http://mina.apache.org/vysper, but it doesn't show up there? Yet, if I
click on "Edit", I see the content?
Would it be possible to change the Atlassian logo on our space? I'd
like to
Hi!
On Sun, Aug 16, 2009 at 08:35, Niklas Gustavsson wrote:
> On Sun, Aug 16, 2009 at 8:31 AM, Niklas Gustavsson
> wrote:
>>> Why is it better to return a null? If a XML element has no namespace
>>> declared, it lies in the "empty" namespace, so a empty string would
>>> conform to the standard.
>
Hi!
The demo application has finally reached its "feature complete" state. You can
- Login (the server accepts user1, user2, user3 all with password "password1")
- Discover all nodes on the server
- See whether the user is the owner
- See if the user is subscribed
- Subscribe and unsubscribe
Hi!
Since the change of rev802821 (null instead of empty string for
namespaces) I'm getting NullPointer Exceptions for my testcases
(coming from Render.java), they are not specific to my code (as far as
I can see) but don't come up with the test-cases of vysper-core.
Why is it better to return a
ubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
Priority: Minor
We want to be able to run more than one pubsub module on one server. Verify
that no collisions occur.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment t
Implement XEP-0114 (Component Protocol)
---
Key: VYSPER-174
URL: https://issues.apache.org/jira/browse/VYSPER-174
Project: VYSPER
Issue Type: New Feature
Reporter: Michael Jakl
[
https://issues.apache.org/jira/browse/VYSPER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-173:
---
Assignee: Michael Jakl
> Introduce a constructor for the PublishSubscribeModule to ena
/VYSPER-173
Project: VYSPER
Issue Type: Bug
Components: XEP0060 PubSub
Reporter: Michael Jakl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi!
On Fri, Aug 14, 2009 at 07:57, Niklas Gustavsson wrote:
> 2009/8/13 Michael Jakl :
>> On Thu, Aug 13, 2009 at 20:06, Niklas Gustavsson wrote:
> Well, the whole purpose of Spring is to enable being able to configure
> things like this, so I don't think there is a problem
Hi!
On Thu, Aug 13, 2009 at 10:16, Niklas Gustavsson wrote:
> On Thu, Aug 13, 2009 at 10:06 AM, Michael Jakl wrote:
> Well, that's no good. Can you try again with the stock JARs? if that
> doesn't work, can you find out what the differences are so that we can
> keep pa
Hi!
On Thu, Aug 13, 2009 at 10:28, Niklas Gustavsson
> No uploaded into our temporary Maven repo:
> http://people.apache.org/~ngn/vysper-repo/jivesoftware/smackx-pubsub/1.0-20090813101732-vysper/
>
> I took some liberties at fiddling with the POM so get the build
> working and align it with the ot
Hi!
On Thu, Aug 13, 2009 at 20:06, Niklas Gustavsson wrote:
> On Thu, Aug 13, 2009 at 3:48 PM, wrote:
>> +
>
> Please note that the MUC module will require a constructor parameter
> that sets the domain on which the MUC module will listen for stanzas.
> Also, user will probably wa
On Thu, Aug 13, 2009 at 10:31, Niklas Gustavsson wrote:
> On Thu, Aug 13, 2009 at 10:25 AM, Michael Jakl wrote:
>>> How does that handle passing a parameter?
>>
>> ServerMain[1] checks if a property "vysper.add.module" is present and
>> loads the given class
Hi!
On Thu, Aug 13, 2009 at 10:16, Niklas Gustavsson wrote:
> On Thu, Aug 13, 2009 at 10:06 AM, Michael Jakl wrote:
>> The smackx-pubsub has special versions of smack and smackx (also
>> called 3.1.0). It *might* work with the stock libs, yet, the last time
>> I tried I
Hi!
On Thu, Aug 13, 2009 at 09:55, Niklas Gustavsson wrote:
> On Thu, Aug 13, 2009 at 9:41 AM, Michael Jakl wrote:
>> My program needs this:
>> http://github.com/squaremo/smackx-pubsub/tree/master
>> with its "special" install procedure. Maybe we could upload this
Hi!
On Thu, Aug 13, 2009 at 09:51, Emmanuel Lecharny wrote:
> Michael Jakl wrote:
> Just wondering,
>
> as you are now a committer, why don't you simply work in a sandbox, instead
> of having your code in a private branch ?
I made some throw-away example applications not
Hi!
Slowly the code approaches a state where I'd like to upload it into the svn. I
think it would make sense to mavenize it beforehand, but I need help for
that.
My program needs this:
http://github.com/squaremo/smackx-pubsub/tree/master
with its "special" install procedure. Maybe we could upload
On Tue, Aug 11, 2009 at 16:39, Bernd Fondermann wrote:
> Michael Jakl wrote:
>> On Mon, Aug 10, 2009 at 22:39, Niklas Gustavsson wrote:
>>> On Mon, Aug 10, 2009 at 10:31 PM, Michael Jakl
>>> wrote:
>>> I would say that the module should deal with that. So, sub
Hi!
On Mon, Aug 10, 2009 at 22:39, Niklas Gustavsson wrote:
> On Mon, Aug 10, 2009 at 10:31 PM, Michael Jakl wrote:
> I would say that the module should deal with that. So, subdomain
> routing first. Everything matching the subdomain goes to the handler
> dic
Hi!
On Mon, Aug 10, 2009 at 22:15, Niklas Gustavsson wrote:
> On Mon, Aug 10, 2009 at 9:54 AM, Michael Jakl wrote:
> So, in addition to the component support (using the component
> protocol), how about we allow for registering modules with a
> subdomain? For example, adding a XMPPServ
Hi!
On Sun, Aug 9, 2009 at 22:35, Niklas Gustavsson wrote:
> In the MUC XEP, implementations should also support the old groupchat
> protocol. This was defined before the extension-based-on-namespaces
> approach was invented and thus use regular stanzas without namespaces,
> for example:
> Enter a
Hi!
On Fri, Aug 7, 2009 at 16:20, Bernd Fondermann wrote:
> Michael Jakl wrote:
>> The extension is completely agnostic about the "to" address, it'll
>> happily take no "to" address as well (subdomain installation).
>
> So to have two pubsubs running
Hi!
On Fri, Aug 7, 2009 at 14:27,
bernd.fondermann wrote:
> You are making great progress on PubSub, as far as I can see.
Thanks!
> Is there any a dedicated pubsub entity responsible for receiving all the
> pubsub stanzas, or can that be any entity?
The extension is completely agnostic about t
Hi!
On Thu, Aug 6, 2009 at 12:30, Bernd
Fondermann wrote:
> As a lazy guy, who doesn't want to look into how smack-pubsub works
> ATM, please tell me, what's this lib doing /beyond/ supporting the
> creation of pubsub stanzas?
It gives a nice interface to most of the features without the need to
On Thu, Aug 6, 2009 at 10:08, Bernd
Fondermann wrote:
> On Wed, Aug 5, 2009 at 20:57, Michael Jakl wrote:
>> On Wed, Aug 5, 2009 at 16:25, Niklas Gustavsson wrote:
>> How shall we cope with the special smack libs? It seems that the
>> required smack lib is from the develo
[
https://issues.apache.org/jira/browse/VYSPER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-171.
-
Resolution: Fixed
Implemented in rev801570.
> Retrieve Affiliations (XEP-0060
[
https://issues.apache.org/jira/browse/VYSPER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-171:
Assignee: Michael Jakl
> Retrieve Affiliations (XEP-0060
Hi!
On Wed, Aug 5, 2009 at 11:35, Bernd Fondermann wrote:
> My proposal is to implement a simple Swing application, featuring:
> + a simple UI, with the following forms:
> a. JID edit field (EF), hostname EF, password EF, "login" button
> b. Node name EF, "subscribe" button, "unsubscribe" button
[
https://issues.apache.org/jira/browse/VYSPER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-85.
Resolution: Fixed
Fixed in rev801534.
> Retrieve subscriptions for LeafNodes (XEP-0060
Hi!
On Wed, Aug 5, 2009 at 22:12, Niklas Gustavsson wrote:
> On Wed, Aug 5, 2009 at 8:57 PM, Michael Jakl wrote:
>> How shall we cope with the special smack libs? It seems that the
>> required smack lib is from the development branch.
>>
>> For reference the URL
On Wed, Aug 5, 2009 at 16:25, Niklas Gustavsson wrote:
> On Wed, Aug 5, 2009 at 2:04 PM, Bernd
> Fondermann wrote:
>>> Where should I put the code?
>>
>> Anyone objecting to mina/sandbox/vysper/trunk/demo/pubsub/client ?
>
> Looks good to me. Will be interesting to have a go playing with the
> pubs
Reporter: Michael Jakl
http://xmpp.org/extensions/tmp/xep-0060-1.13.html#entity-affiliations
--
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-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-158.
-
Resolution: Fixed
Fixed in rev801238
Introduced the concept of "affiliation" and
Hi!
On Wed, Aug 5, 2009 at 14:04, Bernd
Fondermann wrote:
> On Wed, Aug 5, 2009 at 13:36, Michael Jakl wrote:
>> Even though I've got more experience with webapps than any other UI
>> technology, they would not be able to show the advantages of the
>> pubsub approach
Hi!
On Wed, Aug 5, 2009 at 11:35, Bernd Fondermann wrote:
> As the GSoC'09 is nearing 'pencils down' state, I'm thinking about how
> to showcase PubSub in an easy way. New features are not critical, AFAIAC.
Thanks! I was just plotting how to integrate the various access-models
which seems more tr
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-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-90.
Resolution: Later
For the time being we stick with this variant:
* Note: A service MAY allow any
: Sub-task
Components: XEP0060 PubSub
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-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-153:
---
Assignee: Michael Jakl
> Configure a Node (XEP-0060
[
https://issues.apache.org/jira/browse/VYSPER-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-152:
---
Assignee: Michael Jakl
> Implement the access-authorize access-mo
[
https://issues.apache.org/jira/browse/VYSPER-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-150:
---
Assignee: Michael Jakl
> Decentralize the collection of supported featu
[
https://issues.apache.org/jira/browse/VYSPER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-159:
Component/s: XEP0060 PubSub
> Introduce the subscription states (none, pending, unconfigu
060 PubSub
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-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-151:
---
Assignee: Michael Jakl
> Fix and extend "affi
[
https://issues.apache.org/jira/browse/VYSPER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-159:
---
Assignee: Michael Jakl
> Introduce the subscription states (none, pending, unconfigu
: XEP0060 PubSub
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-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl reassigned VYSPER-158:
---
Assignee: Michael Jakl
> Introduce the various affiliations a user can h
Issue Type: Sub-task
Reporter: Michael Jakl
At least "none", "pending", and "subscribed" should be available.
--
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-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-158:
Parent Issue: VYSPER-151 (was: VYSPER-152)
> Introduce the various affiliations a user can h
[
https://issues.apache.org/jira/browse/VYSPER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated VYSPER-151:
Description: Currently there is no "affiliations" concept in the pubsub
extens
PubSub
Reporter: Michael Jakl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Type: Improvement
Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
Currently the configuration of the PubSub extension is done via state variables
which is suboptimal, a better solution might be to use the RuntimeContext for
keeping track
[
https://issues.apache.org/jira/browse/VYSPER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736539#action_12736539
]
Michael Jakl commented on VYSPER-149:
-
Good point, I'll dig into it.
[
https://issues.apache.org/jira/browse/VYSPER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-149.
-
Resolution: Fixed
Removed the sender and receiver variables. I'm not happy with declarin
[
https://issues.apache.org/jira/browse/VYSPER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-8.
-
Resolution: Fixed
Implemented all "REQUIRED" features.
> Implement XEP-0060 Publish Subscr
[
https://issues.apache.org/jira/browse/VYSPER-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-56.
--
Resolution: Duplicate
Duplicate of VYSPER-153 (moved up)
> Configure a Node (XEP-0060
Configure a Node (XEP-0060 8.2)
---
Key: VYSPER-153
URL: https://issues.apache.org/jira/browse/VYSPER-153
Project: VYSPER
Issue Type: Improvement
Components: XEP0060 PubSub
Reporter: Michael
Reporter: Michael Jakl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Introduce "affiliations"
Key: VYSPER-151
URL: https://issues.apache.org/jira/browse/VYSPER-151
Project: VYSPER
Issue Type: Improvement
Components: XEP0060 PubSub
Reporter: Mi
PubSub
Reporter: Michael Jakl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi!
I'm currently plotting the features and tasks for the coming weeks. I've
summarized the completed, planned and "not yet planned" features on our
Wiki[1].
My current plan would be to
1) Implement "affiliations"
2) Implement the "authorize" access-model
3) Make the features configurable
4)
Hi!
Two cool pubsub related projects popped up while I was away:
Wordpress now offers notifications via Pubsub
http://andy.wordpress.com/2009/07/16/real-time-wordpress-com-subscription/
AnyEvent::XMPP::Ext::Pubsub a Perl module that implements XEP-0060
http://search.cpan.org/~elmex/AnyEvent-XMPP
Hi!
On Tue, Jul 7, 2009 at 11:46, Michael Jakl wrote:
> Hi!
>
> On Tue, Jul 7, 2009 at 11:18, Bernd Fondermann wrote:
>>> Take the sender address either from the "from" attribute provided in the
>>> stanza or, if it is not present, take the JID from the
Hi!
On Tue, Jul 7, 2009 at 12:06, Bernd Fondermann wrote:
> Michael Jakl wrote:
>> Currently it should (why not?), but as soon as we allow components to
>> have different domains it doesn't anymore.
>
> That's what I had in mind. What if the pubsub is addressed a
Hi!
On Tue, Jul 7, 2009 at 11:21, Bernd Fondermann wrote:
>> Don't trust the sender with the "to" address, use the one in the
>> sessionContext.
>
> Now _you_ are getting overly defensive. ;-)
>
> If my mind serves me right, the to address has been checked before (in
> ProtocolWorker?), so it's s
Hi!
On Tue, Jul 7, 2009 at 11:18, Bernd Fondermann wrote:
>> Take the sender address either from the "from" attribute provided in the
>> stanza or, if it is not present, take the JID from the initiating entity.
>
> I'd like to propose to move
> AbstractPublishSubscribeIQHandler.getFromAddress()
Hi!
On Tue, Jul 7, 2009 at 09:48, Julien Vermillard wrote:
> Le Tue, 07 Jul 2009 09:42:15 +0200,
> Emmanuel Lecharny a écrit :
>> Michael Jakl wrote:
>> > Reading Ashish's post about the Wiki reminded me to ask for editing
>> > Karma for a sub-page of the Vy
Hi!
Reading Ashish's post about the Wiki reminded me to ask for editing Karma for a
sub-page of the Vysper Wiki (vysper/extensions/pubsub for example).
Cheers,
Michael
Hi!
On Mon, Jul 6, 2009 at 10:10, Bernd Fondermann wrote:
> Michael Jakl wrote:
>> On Mon, Jul 6, 2009 at 07:01, Bernd
>> Fondermann wrote:
>>> On Sun, Jul 5, 2009 at 16:38, Michael Jakl (JIRA) wrote:
>>>> Actually I don't think immutable object make m
[
https://issues.apache.org/jira/browse/VYSPER-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl closed VYSPER-96.
--
Resolution: Fixed
> getNamespace and constructors with a "namespace" parameter are meant f
Hi!
On Mon, Jul 6, 2009 at 07:30, Bernd Fondermann wrote:
> Michael Jakl wrote:
>> Is there a specific reason for the namespace parameter in XMLElement?
>> Otherwise
>> I'd beg remove it (looking at the time it took me to find the bug).
>
> We have to take a look
Hi!
On Mon, Jul 6, 2009 at 07:01, Bernd
Fondermann wrote:
> On Sun, Jul 5, 2009 at 16:38, Michael Jakl (JIRA) wrote:
>> Actually I don't think immutable object make much sense in an imperative
>> language, even though I know the advantages of immutable objects due to my
ey: VYSPER-96
URL: https://issues.apache.org/jira/browse/VYSPER-96
Project: VYSPER
Issue Type: Bug
Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
Priority: Critical
A recent discussion br
1 - 100 of 277 matches
Mail list logo
