On Mon, Sep 8, 2008 at 10:34 PM, Markus KARG <markus.karg_at_gmx.net> wrote:
>> Well, firstly you were pointing to standards :) so I thought of
>> suggesting SIP :).
>
> In fact, the IM extension of SIP that you need to do that is not a standard
> yet but is currently discussed in the IETF working group. So that use of SIP
> is not a standard, just like XMPP. Both have the same status. Only SIP in
> it's original form (session initiation) is a standard.
>
I see, then probably I misunderstood, where it said that in "Aug 2007
Conclusion of SIMPLE".
>> Secondly, I could not agree more that its a bit
>> off-topic, I hope the community does not mind.
>
> I think they will enjoy our discussion. :-)
>
I certainly hope so :).
>> Thirdly, what we are
>> planning includes Presence, Voice/Video over IP, subscription to
>> different type of services and service integration with telcos, so for
>> us in a more integrated manner SIP was solving the requirement in a
>> better way.
>
> I see but this is completely different to simple XML message pushing that
> would be able to handle anything, unrelated to the specific use case that
> you have. The XMPP idea is to be able to push any information. It is not
> telco related at all. So it is much better suited for non-human IM, I think.
>
I agree and also have to say that SIP SIMPLE can do the same, but it
is not only limited to XML, one can also transmit custom content if
required, speaking generally that is.
> I do not say that XMPP is well suited for your specific need, but I would
> say that it is better suited for all the other use cases where the endpoints
> are not humans but services, and where the transported information is simple
> XML information and not video streams.
>
IMHO, both are similar...
>> Saying so, I have to say that same thing can be achieved using XMPP as
>> well, one can actually choose either and I stress that I was not
>> making a comparison, but just putting forward an option.
>
> I see. Sorry then I misunderstood your posting. I am looking for a general
> purpose protocol that a future API can wrap to push any kind of information.
>
Thanks for understanding my viewpoint :). In general, if its
server-2-server communication and update is required in push manner
IMHO, Comet could be extremely useful. If push is required from
server-2-client XMPP/SIP is better suited.
> Sorry if not responding in the next days -- have to leave to Paris now. :-)
>
Have a nice time in Paris. Its an extremely beautiful city...
Best regards,
Imran
> CU
> Markus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
--
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: imran_at_smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557