Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change 
notification.

The following page has been changed by Deepal:
http://wiki.apache.org/ws/FrontPage/Axis2/hackathon_12_06

------------------------------------------------------------------------------
  
        [15:40] Deepal: any one will use it
  
+       gdaniels: the question is what does someone have to do to make a new 
transport
+       
+ [15:45]       gdaniels: which you just answered :)
+ 
+       [15:45] gdaniels: sure
+ 
+       [15:46] gdaniels: so maybe we should consider moving the transports 
we've got except HTTP into library jars
+ 
+       [15:46] gdaniels: ?
+ 
+       [15:46] Deepal: I would say even HTTP into the same place
+ 
+       [15:46] gdaniels: this gets into the packaging discussion we had ages 
ago
+ 
+       [15:46] Deepal: axis2-tansport.jar
+ 
+       [15:47] gdaniels: i.e. axis2-minimal.jar has purely core stuff, no 
transports
+ 
+       [15:47] Deepal: which will have all the tarnsport we have
+ 
+       [15:47] Chinthaka: I hope we are talking about things that will happen 
after this week, right?
+ 
+       [15:47] gdaniels: axis2-small.jar has HTTP but nothing else
+ 
+       [15:47] Deepal: oh that rasied a good q
+ 
+       [15:47] Deepal: abt our packaging
+ 
+       [15:47] gdaniels: yes Chinthaka, but I'd like to record it as a JIRA 
maybe
+ 
+       [15:47] Deepal: I think its good idea to talk ant that too
+ 
+       [15:47] gdaniels: 1.4 timeframe
+ 
+       [15:47] gdaniels: for now bloated jars are the least of our problems :)
+ 
+       [15:48] Chinthaka: Glen : +1. But make sure you get permission from 
Deepal as he might mark it as won't fix later ;)
+ 
+       [15:48] gdaniels: lolol
+ 
+       [15:48] Deepal: :)
+ 
+       [15:52] Deepal: hmm , I wonder its the good idea to ask this q
+ 
+       [15:52] Deepal: what if intergarte addressing handlers in axis2.xml and 
remove addressing module   :)
+ 
+       [15:59] Chinthaka: Deepal, I think the best place to ask this question 
is mailing list
+       [16:00] gdaniels: Deepal, I'm really torn about that one
+ 
+       [16:00] Deepal: :)
+ 
+       [16:00] Deepal: alredy done
+ 
+       [16:00] gdaniels: I think it makes sense, but addressing.mar is a great 
example of eating our own dog food. :)
+ 
+       [16:00] Deepal: there I m thinking as user
+ 
+       [16:00] Deepal: if I want to have session support , asyn invocation I 
need to go and add addressing module 
+ 
+       [16:00] gdaniels: yep
+ 
+       [16:00] gdaniels: oh
+ 
+       [16:00] gdaniels: well, that's fixable
+ 
+       [16:01] Deepal: and need to create ServiceClient with that
+ 
+       [16:01] gdaniels: STOP using addressing for sessions
+ 
+       [16:01] gdaniels: :)
+ 
+       [16:01] Chinthaka: see this is what I always say
+ 
+       [16:01] gdaniels: asy invocations, though, yes. 
+ 
+       [16:01] Deepal: forget abt the session
+ 
+       [16:01] gdaniels: yap
+ 
+       [16:01] Chinthaka: the answer is not getting addressing in to the core
+ 
+       [16:01] Deepal: how abt the asyn invocation
+ 
+       [16:01] Chinthaka: it is about module deployment easier
+ 
+       [16:01] Deepal: just to have that we need to go and engage addressing
+ 
+       [16:01] gdaniels: how do you make it easier Chinthaka?
+ 
+       [16:01] gdaniels: put your mar on the classpath? :)
+ 
+       [16:01] Deepal: and to do so we need to create service client with 
repository
+ 
+       [16:02] Deepal: ???
+ 
+       [16:02] Chinthaka: well first
+ 
+       [16:02] Deepal: I think addressing is core part of Axis2
+ 
+       [16:02] Chinthaka: Deepal why do you wanna get addressing in to core
+ 
+       [16:02] Deepal: its like Dispatchers in the Axis2
+ 
+       [16:02] Chinthaka: no it is not
+ 
+       [16:03] Deepal: for me addressing handlers and Dispatchers are the same
+ 
+       [16:03] Chinthaka: core can not work without dispatching
+ 
+       [16:03] Chinthaka: but core can work without addressing
+ 
+       [16:03] gdaniels: you can't easily do two channel req/resp without 
addressing
+ 
+       [16:03] Deepal: and you have agree with me we have lot of dependcey in 
core on addressing
+ 
+       [16:03] Chinthaka: Glen agree
+ 
+       [16:03] Chinthaka: but lots of people still use sync
+ 
+       [16:03] gdaniels: aside from that, it's not core
+ 
+       [16:03] jaliya: yes
+ 
+       [16:03] Chinthaka: and remember people are still satisfied with 
addressing
+ 
+       [16:04] gdaniels: the MODEL is core (the dependencies Deepal is talking 
about)
+ 
+       [16:04] Chinthaka: which mainly support sync invocations
+ 
+       [16:04] jaliya: they all say, sync works
+ 
+       [16:04] gdaniels: but not the headers, or the handlers
+ 
+       [16:04] jaliya: and once they try async stuff they face problems
+ 
+       [16:04] sanjiva: OT question: does anyone have Chathura (staff @ MRT)'s 
email addr?? I need to send him the question
+ 
+       [16:04] jaliya: and complains
+ 
+       [16:04] jaliya: most because of the configuration
+ 
+       [16:04] Deepal: sanjiva ????
+ 
+       [16:04] sanjiva: sorry guys ;-)
+ 
+       [16:04] Deepal: cool
+ 
+       [16:04] sanjiva: I did say "OT" at the front ....
+ 
+       [16:04] Chinthaka: :)
+ 
+       [16:05] gdaniels: lol
+ 
+       [16:05] Chinthaka: what I would say is make module deployment easier or 
understandable to the users
+ 
+       [16:05] Deepal: when you type OT I though Oxygen Tank :)
+ 
+       [16:05] sanjiva: oh sorry! Off Topic!
+ 
+       [16:06] sanjiva: if addr is core, how do we prevent those pesky headers 
from appearing by default? or are u suggesting that we should leave it on for 
+ requests by default?
+       [16:06] sanjiva: (for responses we can sense and see .. if the req had 
addr then we put it too)
+ 
+ 
+       [16:06] sanjiva: s/addr is core/addr is engaged by default/
+ 
+       [16:07] Chinthaka: woohoooooooooo
+ 
+       [16:07] Chinthaka: I just won the war !!
+ 
+       [16:07] sanjiva: not just the battle but the whole war?? wow
+ 
+       [16:08] Chinthaka: hehe :)
+ 
+       [16:08] sanjiva: give a call to GB; he needs some strategists .. 
+ 
+       [16:08] Chinthaka: I was kidding
+ 
+       [16:08] Chinthaka: GB?
+ 
+       [16:08] jaliya: Gotabya
+ 
+       [16:08] sanjiva: no :) the democratically elected (and democratically 
re-elected) US president ;-)
+ 
+       [16:08] jaliya: ?
+ 
+       [16:08] jaliya: :)
+ 
+       [16:08] sanjiva: dumbya
+ 
+       [16:09] sanjiva: ok I'll shut up; this is what happens when its nearly 
1:45am and the exam is in a few hrs and I am still not done.
+ 
+       [16:10] Deepal: ok developers won , user lost :(
+ 
+       [16:10] srinathp: :)
+ 
+       [16:10] Deepal: ist should be the other way round
+ 
+       [16:32] srinathp: Shall we do no fix for 
https://issues.apache.org/jira/browse/AXIS2-1134. my last comment was <snip>I 
purposed not to support 
+ this. It is not clear how Output stream is to be stored (serialized), and 
even we though able to do it, OS resources will not be avalible for ever. 
Supporting this will be 
+ 
+ big hassle and it will lead to many future problems.</snip>
+       [17:00] chathura: ok guys i am done for the day
+ 
+       [17:01] chathura: see you all tomorrow
+ 
+       [17:02] chathura has disconnected
+ 
+       [17:44] srinathp has disconnected: "ChatZilla 0.9.78.1 [Firefox 
1.5.0.5/2006073115]"
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to