ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Update of "Axis2/HackathonDec2005/chatlog" by DeepalJAID
Date Sat, 10 Dec 2005 02:27:14 GMT
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 DeepalJAID:
http://wiki.apache.org/ws/Axis2/HackathonDec2005/chatlog

------------------------------------------------------------------------------
   [11:48]	dims: BUT the problem is for example synapse wants to add dyanmic services on the
fly?
  
   [11:49]	gdaniels: my preference is to make AxisConfiguration read/write, which makes building
in-memory versions,etc, very easy
+  	[15:12]	saminda_ has joined
+ 
+  	[15:12]	Deepal: hI we are back
+ 
+  	[15:19]	sanjiva_ has joined
+ 
+  	[15:19]	sanjiva has disconnected: Read error: 110 (Connection timed out)
+ 
+  	[15:19]	Chinthaka has disconnected: Read error: 110 (Connection timed out)
+ 
+  	[15:20]	Ajith has disconnected: Read error: 113 (No route to host)
+ 
+  	[15:40]	paulfremantle has joined
+ 
+  	[15:47]	dblevins_ has disconnected: "This computer has gone to sleep"
+ 
+  	[15:47]	dims: hi qll
+ 
+  	[15:49]	jsisson has disconnected: Read error: 110 (Connection timed out)
+ 
+  	[15:52]	dims: guys: FYI, see this - http://netzooid.com/blog/2005/12/09/5-cool-xfire-hacks/
+ 
+  	[15:59]	dims has disconnected
+ 
+  	[15:59]	dims has joined
+ 
+  	[16:00]	jsisson has joined
+ 
+  	[16:00]	dims: PING
+ 
+  	[16:00]	dims: oops. sorry about the caps lock
+ 
+  	[16:00]	Chinthaka_: you wanna point us some cool methods one may like to have in Call
?
+ 
+  	[16:01]	dims says me?
+ 
+  	[16:01]	Chinthaka_: I saw another post in that blog, challenging Axis performance. I agree
that we need to work on that too :(
+ 
+  	[16:01]	Chinthaka_: http://netzooid.com/blog/2005/11/03/more-notes-on-soap-and-xfire-performance/
+ 
+  	[16:01]	dims: i'd like to revisit paul's OXM when we get a chance
+ 
+  	[16:01]	dims: i haven't been able to spend time on perf yet
+ 
+  	[16:02]	dims: it's on my TODO list.
+ 
+  	[16:02]	dims: i'll be back in a couple of hours.
+ 
+  	[16:02]	paulfremantle: ok
+ 
+  	[16:03]	paulfremantle: see ya!
+ 
+  	[16:03]	dims: sanjiva has my cell if you guys need something from me (which i doubt!)
+ 
+  	[16:33]	Deepal: disussion on Call
+ 
+  	[16:33]	Deepal: does call per an operation or service invocation
+ 
+  	[16:35]	jsisson has disconnected: Read error: 104 (Connection reset by peer)
+ 
+  	[16:36]	jsisson has joined
+ 
+  	[16:38]	sanjiva_ is now known as sanjiva
+ 
+  	[16:39]	Chinthaka_ is now known as Chinthaka
+ 
+  	[16:39]	Ajith_ is now known as Ajith
+ 
+  	[17:13]	dblevins has joined
+ 
+  	[17:15]	dblevins has disconnected: Client Quit
+ 
+  	[17:16]	dblevins has joined
+ 
+  	[17:22]	jsisson is now known as HeWhoShallNotBeN
+ 
+  	[17:23]	HeWhoShallNotBeN is now known as jsisson
+ 
+  	[17:25]	gdaniels: Discussion re: engaging Modules and AxisService/AxisOperation/AxisMessage...
+ 
+  	[17:26]	gdaniels: 1) The only handler chain that matters is the one in the MessageContext
+ 
+  	[17:26]	gdaniels: 2) The flow when a new MessageContext enters the system is as follows...
+ 
+  	[17:26]	gdaniels:    * Copy the global "template" chain (pre-computed from the system
defined phases) into the MC
+ 
+  	[17:27]	gdaniels:    * Run handlers until dispatch occurs
+ 
+  	[17:27]	gdaniels:    * When you dispatch to a particular point (service/op/msg), do something
like this:
+ 
+  	[17:27]	gdaniels:      if (caching && cachedChain) {
+ 
+  	[17:27]	gdaniels:         copyChainToMessageContext(cachedChain, msgContext);
+ 
+  	[17:28]	gdaniels:         return;
+ 
+  	[17:28]	gdaniels:     }
+ 
+  	[17:28]	gdaniels:     engageMyModules(msgContext.handlerChain);
+ 
+  	[17:28]	gdaniels:     if (caching) {
+ 
+  	[17:29]	gdaniels:         copyChainToCache(msgContext.handlerChain);
+ 
+  	[17:29]	gdaniels:     }
+ 
+  	[17:29]	gdaniels: ...
+ 
+  	[17:30]	gdaniels:      in other words, allow either computing the handlers by engaging
modules, which will always be correct but may be expensive, or caching the computed chains
and writing over the active chain with the cached ones (which doesn't account for dynamic
policy).
+ 
+  	[17:41]	csj has joined
+ 
+  	[17:41]	csj: does axis c support attachments?
+ 
+  	[17:48]	paulfremantle: good question.... i don't know if MTOM is in there yet
+ 
+  	[17:49]	csj: paulfremantle, how about MIME
+ 
+  	[17:51]	paulfremantle: well MTOM will use MIME... but MTOM is the approach to use now
+ 
+  	[17:52]	paulfremantle: hold on
+ 
+  	[17:52]	paulfremantle: let me just ask
+ 
+  	[17:52]	paulfremantle: do you mean axisC++ 1.x or the new axis2/c stuff?
+ 
+  	[17:52]	csj: either, just needs to support binary mime attachments
+ 
+  	[17:53]	csj: I have a server side service in java that accepts mime encapsulated attachments,
but I need a c / c++ client to talk with it.. 
+ 
+  	[17:54]	paulfremantle: ah ok
+ 
+  	[17:54]	csj: I was using a java client for a while but for reasons beyond my control they
need to be in c/c++ new
+ 
+  	[17:55]	csj: s/new/now
+ 
+  	[17:55]	paulfremantle: ok
+ 
+  	[17:55]	paulfremantle: i understand
+ 
+  	[17:56]	paulfremantle: hold on a min
+  	[17:56]	csj: sure..
+ 
+ 
+  	[17:59]	paulfremantle: so... there is some limited support in AxisC++ 1.6 alpha
+ 
+  	[17:59]	csj: still huh... server side only really huh?
+ 
+  	[18:01]	paulfremantle: no both client and server
+ 
+  	[18:01]	paulfremantle: but not sure how good it is
+ 
+  	[18:02]	csj: are you a user or developer of axis?
+ 
+  	[18:03]	paulfremantle: i worked on the axisc++ stuff but haven't been involved in it recently
+ 
+  	[18:03]	paulfremantle: we are rebuilding it in pure C with a cleaner design
+ 
+  	[18:04]	paulfremantle: but i can find out the status for you no problem
+ 
+  	[18:04]	csj: that would be great, I dont mind helping to get attachments working but it
seems as if the development team is a close group of people..
+ 
+  	[18:05]	paulfremantle: so the main contributors to AxisC++ are the IBM team
+ 
+  	[18:05]	paulfremantle: they ship a packaged version of it:
+ 
+  	[18:05]	paulfremantle: http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24009162&loc=en_US&cs=utf-8&lang=en
+ 
+  	[18:06]	paulfremantle: whats the Java server?
+ 
+  	[18:06]	csj: tomcat, my guess is your an IBMer :P
+ 
+  	[18:06]	paulfremantle: no but i used to be
+ 
+  	[18:06]	paulfremantle: is it Axis Java on Tomcat?
+ 
+  	[18:07]	csj: yup..
+ 
+  	[18:08]	paulfremantle: ok... so early next year we hope to support Axis2/C-->Axis2/Java
with attachments
+ 
+  	[18:09]	csj: ok..
+ 
+  	[18:10]	paulfremantle: if you give me an email i'll get back to you
+ 
+  	[18:10]	csj: next year?
+ 
+  	[18:11]	csj: well it is Dec :P
+ 
+  	[18:11]	paulfremantle: no about the existing axisC++ support
+ 
+  	[18:12]	paulfremantle: or send me an email to paul@wso2.com and i'll find out for you
+ 
+  	[18:12]	paulfremantle: one of our guys was one of the key devs on AxisC++ 1.x and he will
know
+ 
+  	[18:12]	csj: ok, great..
+ 
+  	[18:13]	paulfremantle: no problem
+ 
+  	[18:14]	csj: why are making the change to c rather then c++
+ 
+  	[18:15]	paulfremantle: ahha
+ 
+  	[18:15]	paulfremantle: so we had a lot of people 
+ 
+  	[18:15]	paulfremantle: who 
+ 
+  	[18:15]	paulfremantle: had strange C++ environments
+ 
+  	[18:15]	paulfremantle: or unnatural hatred of C++ etc
+ 
+  	[18:16]	paulfremantle: and so since we had to do a lot of rework
+ 
+  	[18:16]	paulfremantle: we figured C was more likely to be universally acceptable
+ 
+  	[18:16]	csj: how is the c version going to support ssl?
+ 
+  	[18:16]	paulfremantle: i.e. C++ users have no problems with C.. but not so clearly vice
versa
+ 
+  	[18:18]	paulfremantle: well we will probably put in an abstraction
+ 
+  	[18:18]	paulfremantle: and then use openssl
+ 
+  	[18:20]	paulfremantle: whats your opinion of the c/c++ issue
  
   [11:49]	gdaniels: dims: +1
  

Mime
View raw message