Yep, its worth to try, most resources on the net says that MTOM is better :)
On 3/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Good point - all I have to do is get the server guys to do the switch :-( Which may take a while. Although with gsoap supporting MTOM, maybe I'll have some luck I presume DIME -> MTOM is a no go (worth asking anyway!) "Tomek Sztelak" <[EMAIL PROTECTED]> 08/03/2007 16:32 Please respond to [email protected] To [email protected] cc Subject Re: [xfire-user] xFire and gSOAP On 3/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Only thing is the GSOAP uses DIME attachments.. (although I'd be happy to > be corrected on this). > > But the minute XFire does DIME, I'm moving from Axis 1.4! > James Hmm, GSOAP can also use MTOM attachments..so maybe its better idea to move from dime to mtom and then from axis to xfire :D > > > > > "Tomek Sztelak" <[EMAIL PROTECTED]> > 08/03/2007 16:25 > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Re: [xfire-user] xFire and gSOAP > > > > > > > On 3/8/07, a a <[EMAIL PROTECTED]> wrote: > > I would like to have come informations about the interoperability > between xFire and gSOAP. > > > > My goal is to do a communication between a gSOAP server and a xFire > client > > > > is it possible ? > > This is a goal of webservices, to allow communication between > different systems and languages, so until you stay away from > RPC/encoded and Map's , everything should work fine ( in theory ;). > I've never used gSoap but it claims that its WS-I compliant, so > probably you won't have much problems. > > > > > xFire is asynchronus ? > > XFire can be asynchronous if you use JMS transport. > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > > This email is intended solely for the use of the named addressee(s). Any > unauthorised disclosure, copying or distribution of the confidential > information contained therein, or the taking of any action based on it, is > prohibited. The sender disclaims any liability for the integrity of this > email. Legally binding declarations must be in written form. > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email This email is intended solely for the use of the named addressee(s). Any unauthorised disclosure, copying or distribution of the confidential information contained therein, or the taking of any action based on it, is prohibited. The sender disclaims any liability for the integrity of this email. Legally binding declarations must be in written form. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
