Paul, Vacation took me away for 3 weeks. I'm back now for SOAP over SIP..
I think it will be a leg up for axis2 to have support for the SIP transport independently. SIP messaging is very close to WS-Eventing in which a SIP INVITE can yield several messages going back to the client. Its all messaging really ;) but we should decide what approach we should take. Do you want to move to axis-dev? Samir --- Paul Fremantle <[EMAIL PROTECTED]> wrote: > Samir > > One more thing we should look at. It seems like the > HTTP code we use > for non-blocking (HTTPCore) already also has some > limited support for > SIP! > > This would mean we would have to code directly to > that API (i.e. we > wouldn't use the SIP Servlet model). However, this > seems to me to have > two key benefits. > > 1) We could probably start from the NHTTP transport > and therefore > re-use a lot of code > 2) We'd end up with a non-blocking SIP transport > which is a "good > thing" (more efficient) > > Also the folks over at HTTPCore are incredibly > helpful. > > Paul > > > On Dec 23, 2007 4:58 AM, Demetris G > <[EMAIL PROTECTED]> wrote: > > > > Likewise Paul - thanks for the pointer. > > > > > > Paul Fremantle wrote: > > > Good point! > > > > > > SIP is basically the standard for doing Voice > Over Internet Protocol > > > (VOIP) that is used by systems like Vonage, > Asterisk, etc to provide > > > phoning on the internet. > > > > > > Merry Christmas and Happy New Year to everyone! > > > > > > Paul > > > > > > On Dec 22, 2007 8:29 AM, Demetris G > <[EMAIL PROTECTED]> wrote: > > > > > >> Echoing Paul's "I didn't know anything about > coding SIP in Java" and further > > >> seeing these terms flying around this list for > a long time now, wouldn't > > >> be so > > >> much nicer for the rest of us who are willing > to learn, for whoever is > > >> asking > > >> a Q out of the list to also spend 3.5 secs to > write down a definition of the > > >> term they are requesting help with? I hear > POJO, MOJO, GOJO, blah blah > > >> and MTOM and this and that and now SIP ... oh > sure, everything is just > > >> a google away but putting it in the context of > the list educates all of > > >> us. Just > > >> a friendly suggestion ... > > >> > > >> SIP - away my friends ... > > >> > > >> > > >> > > >> Paul Fremantle wrote: > > >> > > >>> Samir > > >>> > > >>> Ok so I didn't know anything about coding SIP > in Java :) > > >>> > > >>> Basically, yes we need a reference impl of the > SIPServlet spec > > >>> (assuming that it has a valid license), and we > also need a client SIP > > >>> stack too. > > >>> > > >>> It seems like this is what we need: > https://jain-sip.dev.java.net/ tho > > >>> I can't find out what license that is under. > > >>> > > >>> Also I found an interesting alternative to the > SIP Servlet which is the JIPlet: > > >>> > http://www.cafesip.org/projects/jiplet/index.html > > >>> > > >>> However, I'm not sure its really worth using > JIPlet over the SIP > > >>> servlet. What are your thoughts? > > >>> > > >>> Paul > > >>> > > >>> PS. In HTTP the equivalent is the servlet plus > the Commons HTTPClient. > > >>> However, the newer non-blocking HTTP is based > on an Apache library > > >>> called HTTPCore which provides a non-blocking > IO version of HTTP. > > >>> > > >>> > > >>> > > >>> On Dec 22, 2007 1:08 AM, samir shaikh > <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>>> Paul, > > >>>> > > >>>> What do you mean by base SIP function? Do you > mean we > > >>>> need some reference implementation of the > sipservlet > > >>>> specification? can you tell me what it is for > http so > > >>>> then i can understand what we are looking for > here. > > >>>> > > >>>> > > >>>> Samir > > >>>> > > >>>> --- Paul Fremantle <[EMAIL PROTECTED]> wrote: > > >>>> > > >>>> > > >>>> > > >>>>> Samir > > >>>>> > > >>>>> The usual first step is to identify a > library that > > >>>>> can be used to > > >>>>> provide the base SIP function. Also the > library > > >>>>> needs to be compatible > > >>>>> with Apache Licensing - i.e. it must be Open > Source > > >>>>> and also not GPL > > >>>>> (but LPGL is ok). Obviously if we can find > one under > > >>>>> the Apache or BSD > > >>>>> license that is best. > > >>>>> > > >>>>> Paul > > >>>>> > > >>>>> On Dec 21, 2007 12:14 AM, samir shaikh > > >>>>> <[EMAIL PROTECTED]> wrote: > > >>>>> > > >>>>> > > >>>>>> Paul, > > >>>>>> > > >>>>>> I'll be happy to team up with you on this. > If you > > >>>>>> could lay out for me what is involved that > will be > > >>>>>> great. We could have something based off of > the > > >>>>>> sipservlet specification. Meanwhile, I can > also > > >>>>>> research the existing transports as part of > > >>>>>> > > >>>>>> > > >>>>> synapse. > > >>>>> > > >>>>> > > >>>>>> Samir > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> --- Paul Fremantle <[EMAIL PROTECTED]> > wrote: > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Samir > > >>>>>>> > > >>>>>>> We do not have a SIP transport for SOAP in > > >>>>>>> > > >>>>>>> > > >>>>> Axis2. > > >>>>> > > >>>>> > > >>>>>>> However, if you > > >>>>>>> would be willing to help write one we > would be > > >>>>>>> > > >>>>>>> > > >>>>> very > > >>>>> > > >>>>> > > >>>>>>> happy to help. > > >>>>>>> From my knowledge of SIP it would make a > good > > >>>>>>> transport and has some > > >>>>>>> benefits over HTTP. If you want to see how > Axis2 > > >>>>>>> transports are > === message truncated === ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
