Volunteers for implementing JXTA support? (was: jxta and address book)

Hey Nick, all

Took me a while huh . Well they
say - better late than never, so here 
goes.

buzz lightyear wrote:
> I just suddenly realised that for jxta, a peerid is
also needed for each 
> peer. This is the ID you use to contact another peer
with.

All protocols in the SIP Communicator are represented by the

ProtocolProviderService package. The package contains an
interface 
called ContactID. This interface is implemented by the
various protocols 
in the way they seem fit or in other words they could just
as well wrap 
the implementation around a PeerID.

Incidentally, I am using the opportunity to ask whether
someone out 
there would be a volunteer to start an implementation of the

ProtocolProviderService over JXTA? I personally think that
this would be 
a very cool thing to do!

Don't be shy! Step forward!

Cheers
Emil



------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

I'd be happy to do this once sip audio/video are in place.

Cheers
Nick


>From: Emil Ivov <emil.ivovgmail.com>
>Reply-To: devsip-communicator.dev.java.net
>To: devsip-communicator.dev.java.net
>Subject: [sip-comm-dev] Volunteers for implementing JXTA
support? (was:  
>jxta and address book)
>Date: Sun, 23 Apr 2006 06:16:31 +0200
>
>Hey Nick, all
>
>Took me a while huh . Well they
say - better late than never, so here 
>goes.
>
>buzz lightyear wrote:
>>I just suddenly realised that for jxta, a peerid is
also needed for each 
>>peer. This is the ID you use to contact another peer
with.
>
>All protocols in the SIP Communicator are represented by
the 
>ProtocolProviderService package. The package contains an
interface called 
>ContactID. This interface is implemented by the various
protocols in the 
>way they seem fit or in other words they could just as
well wrap the 
>implementation around a PeerID.
>
>Incidentally, I am using the opportunity to ask whether
someone out there 
>would be a volunteer to start an implementation of the 
>ProtocolProviderService over JXTA? I personally think
that this would be a 
>very cool thing to do!
>
>Don't be shy! Step forward!
>
>Cheers
>Emil
>
>
>
>--------------------------------------------------------
-------------
>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>

____________________________________________________________
_____
Are you using the latest version of MSN Messenger? Download
MSN Messenger 
7.5 today! http://join.ms
n.com/messenger/overview

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Forgot to ask - when will the sip audio/video be ready?

...... hate to bring this up but ..... we're coming up to
the anniversary at 
the end of May of when sip-communictor 1.0 with sip
audio/video should have 
originally been ready .....

Cheers
Nick


>From: "buzz lightyear" <buzzheavyyearhotmail.com>
>Reply-To: devsip-communicator.dev.java.net
>To: devsip-communicator.dev.java.net
>Subject: RE: [sip-comm-dev] Volunteers for implementing
JXTA support? (was: 
>jxta and addr
>Date: Sun, 23 Apr 2006 14:46:22 +0000
>
>I'd be happy to do this once sip audio/video are in
place.
>
>Cheers
>Nick
>
>
>>From: Emil Ivov <emil.ivovgmail.com>
>>Reply-To: devsip-communicator.dev.java.net
>>To: devsip-communicator.dev.java.net
>>Subject: [sip-comm-dev] Volunteers for implementing
JXTA support? (was:  
>>jxta and address book)
>>Date: Sun, 23 Apr 2006 06:16:31 +0200
>>
>>Hey Nick, all
>>
>>Took me a while huh . Well they
say - better late than never, so here 
>>goes.
>>
>>buzz lightyear wrote:
>>>I just suddenly realised that for jxta, a peerid
is also needed for each 
>>>peer. This is the ID you use to contact another
peer with.
>>
>>All protocols in the SIP Communicator are
represented by the 
>>ProtocolProviderService package. The package
contains an interface called 
>>ContactID. This interface is implemented by the
various protocols in the 
>>way they seem fit or in other words they could just
as well wrap the 
>>implementation around a PeerID.
>>
>>Incidentally, I am using the opportunity to ask
whether someone out there 
>>would be a volunteer to start an implementation of
the 
>>ProtocolProviderService over JXTA? I personally
think that this would be a 
>>very cool thing to do!
>>
>>Don't be shy! Step forward!
>>
>>Cheers
>>Emil
>>
>>
>>
>>----------------------------------------------------
-----------------
>>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>
>________________________________________________________
_________
>Are you using the latest version of MSN Messenger?
Download MSN Messenger 
>7.5 today! http://join.ms
n.com/messenger/overview
>
>--------------------------------------------------------
-------------
>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>

____________________________________________________________
_____
Are you using the latest version of MSN Messenger? Download
MSN Messenger 
7.5 today! http://join.ms
n.com/messenger/overview

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello Nick,

> Forgot to ask - when will the sip audio/video be ready?

It's hard to say. A month or two I guess.

> ...... hate to bring this up but ..... we're coming up
to the
> anniversary at the end of May of when sip-communictor
1.0 with sip
> audio/video should have originally been ready .....

Oh it was originally previewed for the end of January 2005
so the 1 year
anniversary has come and gone.
We're doing what we can, and I think we're already seeing
the light at
the end of the SIP Communicator crisis tunnel!

> I'd be happy to do this once sip audio/video are in
place.

Well, unless you have some other reason, you don't really
need to wait
for them. All that's necessary to implement JXTA instant
messaging and
presence is already there.

Cheers
Emil

>> 
>> Cheers Nick
>> 
>> 
>>> From: Emil Ivov <emil.ivovgmail.com> Reply-To:
>>> devsip-communicator.dev.java.net To:
>>> devsip-communicator.dev.java.net Subject:
[sip-comm-dev]
>>> Volunteers for implementing JXTA support? (was:
jxta and address
>>> book) Date: Sun, 23 Apr 2006 06:16:31 +0200
>>> 
>>> Hey Nick, all
>>> 
>>> Took me a while huh . Well they
say - better late than never,
>>> so here goes.
>>> 
>>> buzz lightyear wrote:
>>>> I just suddenly realised that for jxta, a
peerid is also needed
>>>> for each peer. This is the ID you use to
contact another peer
>>>> with.
>>> All protocols in the SIP Communicator are
represented by the 
>>> ProtocolProviderService package. The package
contains an
>>> interface called ContactID. This interface is
implemented by the
>>> various protocols in the way they seem fit or
in other words they
>>> could just as well wrap the implementation
around a PeerID.
>>> 
>>> Incidentally, I am using the opportunity to ask
whether someone
>>> out there would be a volunteer to start an
implementation of the
>>>  ProtocolProviderService over JXTA? I
personally think that this
>>> would be a very cool thing to do!
>>> 
>>> Don't be shy! Step forward!
>>> 
>>> Cheers Emil
>>> 
>>> 
>>> 
>>>
------------------------------------------------------------
---------
>>>  To unsubscribe, e-mail:
>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>> 
>>
____________________________________________________________
_____ 
>> Are you using the latest version of MSN Messenger?
Download MSN
>> Messenger 7.5 today! http://join.ms
n.com/messenger/overview
>> 
>>
------------------------------------------------------------
---------
>>  To unsubscribe, e-mail:
>> dev-unsubscribesip-communicator.dev.java.net For additional
>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>> 
> 
>
____________________________________________________________
_____ Are
> you using the latest version of MSN Messenger? Download
MSN Messenger
>  7.5 today! http://join.ms
n.com/messenger/overview
> 
>
------------------------------------------------------------
---------
>  To unsubscribe, e-mail:
> dev-unsubscribesip-communicator.dev.java.net For
additional
> commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Emil and All,

I don't know if I can step forward in this case, as I have
alredy said I 
am intending to develop the MSN protocol service. If it is
related, I am 
realy looking forward to help with the
ProtocolProviderService!! I might 
need background information on the design and how it works.

On the build.xml subject (ant task OS specific), I looked
for more and 
in the documentaition I found it is written that writing the
task that 
way (os param) is the suggested way!

I still have to add a call to TestCase.fail() in the case of
a missing 
accounts.properties file as well as print and shortly pause
the output 
on an error message in the console, I hope I can manage ir
real soon!!!!

I found the following site as MSN reference too, it
describes pretty 
well I would say:
http://www.hypothetic.org/docs/msn/general/overview.php

Best regards
Pedro

Emil Ivov wrote:

> Hey Nick, all
>
> Took me a while huh . Well they
say - better late than never, so 
> here goes.
>
> buzz lightyear wrote:
>
>> I just suddenly realised that for jxta, a peerid is
also needed for 
>> each peer. This is the ID you use to contact
another peer with.
>
>
> All protocols in the SIP Communicator are represented
by the 
> ProtocolProviderService package. The package contains
an interface 
> called ContactID. This interface is implemented by the
various 
> protocols in the way they seem fit or in other words
they could just 
> as well wrap the implementation around a PeerID.
>
> Incidentally, I am using the opportunity to ask whether
someone out 
> there would be a volunteer to start an implementation
of the 
> ProtocolProviderService over JXTA? I personally think
that this would 
> be a very cool thing to do!
>
> Don't be shy! Step forward!
>
> Cheers
> Emil
>
>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

I'll put together a rough proposal and a skeleton
ProtocolProviderService 
implementation over the next week or so.

If someone is already working on the sip audeo/video service
then please 
send me a mail - some thought needs to go into the media and
sip 
streams/pipes/sockets etc

Cheers
Nick

>From: Emil Ivov <emil.ivovgmail.com>
>Reply-To: devsip-communicator.dev.java.net
>To: devsip-communicator.dev.java.net
>Subject: Re: [sip-comm-dev] Volunteers for implementing
JXTA support? (was: 
>jxta and addr
>Date: Tue, 25 Apr 2006 04:12:39 +0200
>
>Hello Nick,
>
>>Forgot to ask - when will the sip audio/video be
ready?
>
>It's hard to say. A month or two I guess.
>
>>...... hate to bring this up but ..... we're coming
up to the
>>anniversary at the end of May of when
sip-communictor 1.0 with sip
>>audio/video should have originally been ready .....
>
>Oh it was originally previewed for the end of January
2005 so the 1 year
>anniversary has come and gone.
>We're doing what we can, and I think we're already
seeing the light at
>the end of the SIP Communicator crisis tunnel!
>
>>I'd be happy to do this once sip audio/video are in
place.
>
>Well, unless you have some other reason, you don't
really need to wait
>for them. All that's necessary to implement JXTA
instant messaging and
>presence is already there.
>
>Cheers
>Emil
>
>>>
>>>Cheers Nick
>>>
>>>
>>>>From: Emil Ivov <emil.ivovgmail.com> Reply-To:
>>>>devsip-communicator.dev.java.net To:
>>>>devsip-communicator.dev.java.net Subject:
[sip-comm-dev]
>>>>Volunteers for implementing JXTA support?
(was: jxta and address
>>>>book) Date: Sun, 23 Apr 2006 06:16:31 +0200
>>>>
>>>>Hey Nick, all
>>>>
>>>>Took me a while huh . Well they
say - better late than never,
>>>>so here goes.
>>>>
>>>>buzz lightyear wrote:
>>>>>I just suddenly realised that for jxta,
a peerid is also needed
>>>>>for each peer. This is the ID you use to
contact another peer
>>>>>with.
>>>>All protocols in the SIP Communicator are
represented by the 
>>>>ProtocolProviderService package. The package
contains an
>>>>interface called ContactID. This interface
is implemented by the
>>>>various protocols in the way they seem fit
or in other words they
>>>>could just as well wrap the implementation
around a PeerID.
>>>>
>>>>Incidentally, I am using the opportunity to
ask whether someone
>>>>out there would be a volunteer to start an
implementation of the
>>>>  ProtocolProviderService over JXTA? I
personally think that this
>>>>would be a very cool thing to do!
>>>>
>>>>Don't be shy! Step forward!
>>>>
>>>>Cheers Emil
>>>>
>>>>
>>>>
>>>>--------------------------------------------
-------------------------
>>>>  To unsubscribe, e-mail:
>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>
>>>________________________________________________
_________________ Are you 
>>>using the latest version of MSN Messenger?
Download MSN
>>>Messenger 7.5 today! http://join.ms
n.com/messenger/overview
>>>
>>>------------------------------------------------
---------------------
>>>  To unsubscribe, e-mail:
>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>
>>____________________________________________________
_____________ Are
>>you using the latest version of MSN Messenger?
Download MSN Messenger
>>  7.5 today! http://join.ms
n.com/messenger/overview
>>
>>----------------------------------------------------
-----------------
>>  To unsubscribe, e-mail:
>>dev-unsubscribesip-communicator.dev.java.net For
additional
>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
>
>--------------------------------------------------------
-------------
>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>

____________________________________________________________
_____
Express yourself instantly with MSN Messenger! Download
today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Nick,

buzz lightyear wrote:
> I'll put together a rough proposal and a skeleton
ProtocolProviderService 
> implementation over the next week or so.

Hey hey! Am I glad to hear that!

> If someone is already working on the sip audeo/video
service then please 
> send me a mail - some thought needs to go into the
media and sip 
> streams/pipes/sockets etc

Will do Nick.

Cheers
Emil

> 
> Cheers
> Nick
> 
>> From: Emil Ivov <emil.ivovgmail.com>
>> Reply-To: devsip-communicator.dev.java.net
>> To: devsip-communicator.dev.java.net
>> Subject: Re: [sip-comm-dev] Volunteers for
implementing JXTA support? (was: 
>> jxta and addr
>> Date: Tue, 25 Apr 2006 04:12:39 +0200
>>
>> Hello Nick,
>>
>>> Forgot to ask - when will the sip audio/video
be ready?
>> It's hard to say. A month or two I guess.
>>
>>> ...... hate to bring this up but ..... we're
coming up to the
>>> anniversary at the end of May of when
sip-communictor 1.0 with sip
>>> audio/video should have originally been ready
.....
>> Oh it was originally previewed for the end of
January 2005 so the 1 year
>> anniversary has come and gone.
>> We're doing what we can, and I think we're
already seeing the light at
>> the end of the SIP Communicator crisis tunnel!
>>
>>> I'd be happy to do this once sip audio/video
are in place.
>> Well, unless you have some other reason, you don't
really need to wait
>> for them. All that's necessary to implement JXTA
instant messaging and
>> presence is already there.
>>
>> Cheers
>> Emil
>>
>>>> Cheers Nick
>>>>
>>>>
>>>>> From: Emil Ivov <emil.ivovgmail.com> Reply-To:
>>>>> devsip-communicator.dev.java.net To:
>>>>> devsip-communicator.dev.java.net Subject: [sip-comm-dev]
>>>>> Volunteers for implementing JXTA
support? (was: jxta and address
>>>>> book) Date: Sun, 23 Apr 2006 06:16:31
+0200
>>>>>
>>>>> Hey Nick, all
>>>>>
>>>>> Took me a while huh . Well they
say - better late than never,
>>>>> so here goes.
>>>>>
>>>>> buzz lightyear wrote:
>>>>>> I just suddenly realised that for
jxta, a peerid is also needed
>>>>>> for each peer. This is the ID you
use to contact another peer
>>>>>> with.
>>>>> All protocols in the SIP Communicator
are represented by the 
>>>>> ProtocolProviderService package. The
package contains an
>>>>> interface called ContactID. This
interface is implemented by the
>>>>> various protocols in the way they seem
fit or in other words they
>>>>> could just as well wrap the
implementation around a PeerID.
>>>>>
>>>>> Incidentally, I am using the
opportunity to ask whether someone
>>>>> out there would be a volunteer to start
an implementation of the
>>>>>  ProtocolProviderService over JXTA? I
personally think that this
>>>>> would be a very cool thing to do!
>>>>>
>>>>> Don't be shy! Step forward!
>>>>>
>>>>> Cheers Emil
>>>>>
>>>>>
>>>>>
>>>>>
------------------------------------------------------------
---------
>>>>>  To unsubscribe, e-mail:
>>>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>
>>>>
____________________________________________________________
_____ Are you 
>>>> using the latest version of MSN Messenger?
Download MSN
>>>> Messenger 7.5 today! http://join.ms
n.com/messenger/overview
>>>>
>>>>
------------------------------------------------------------
---------
>>>>  To unsubscribe, e-mail:
>>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>
>>>
____________________________________________________________
_____ Are
>>> you using the latest version of MSN Messenger?
Download MSN Messenger
>>>  7.5 today! http://join.ms
n.com/messenger/overview
>>>
>>>
------------------------------------------------------------
---------
>>>  To unsubscribe, e-mail:
>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
> 
>
____________________________________________________________
_____
> Express yourself instantly with MSN Messenger! Download
today - it's FREE! 
> http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Apologies for not getting back sooner.

I've been thinking about the best approach for using jxta
within 
sip-communicator and I'm beginning to favour some sort of
factory with which 
protocols can register themselves and request pipes/streams
to be created 
between peers - in the sip-communicator context, jxta is
acting as more of a 
transport than a protocol to an external service (yes, the
protocol maybe 
routed back to another sip-communicator).

The jxta protocol/transport will listen to, and broadcast
the presence 
status, of the user, and also respond correctly reflectin
the users contact 
list.

To recap, briefly, on jxta, peers communicate with each
other by initially 
contacting a jxta rendezvous, discover other peers and then
talk directly 
with each other. For those peers that are behind a hard
firewall, they need 
to go through the firewall via a jxta relay.

Jxta  peers start in an initial peergroup and then can
create additional 
peer groups, join the peergroups; create services in any of
the peergroups 
and use the various services offered by other peers via
pipes - sockets or 
messages (messages are xml, with subclasses of byte[] and
string).... and 
sockets chunk everything into byte[] and use the pipes.

So, by offering a jxta factory by which sip, icq etc have
the freedom to 
create any number of streams/pipes between peers and their
respective 
protocols, this, surely, should be flexible enough?

I hope I'm going in the right direction here for everyone?

I'm out for the whole of next week, but intend devoting the
following week 
to writing a skeleton and commiting it (lgpl, of course).

Cheers
Nick


>From: Emil Ivov <emil.ivovgmail.com>
>Reply-To: devsip-communicator.dev.java.net
>To: devsip-communicator.dev.java.net
>Subject: Re: [sip-comm-dev] Volunteers for implementing
JXTA support? (was: 
>jxta and addr
>Date: Tue, 25 Apr 2006 14:39:43 +0200
>
>Hi Nick,
>
>buzz lightyear wrote:
>>I'll put together a rough proposal and a skeleton
ProtocolProviderService 
>>implementation over the next week or so.
>
>Hey hey! Am I glad to hear that!
>
>>If someone is already working on the sip audeo/video
service then please 
>>send me a mail - some thought needs to go into the
media and sip 
>>streams/pipes/sockets etc
>
>Will do Nick.
>
>Cheers
>Emil
>
>>
>>Cheers
>>Nick
>>
>>>From: Emil Ivov <emil.ivovgmail.com>
>>>Reply-To: devsip-communicator.dev.java.net
>>>To: devsip-communicator.dev.java.net
>>>Subject: Re: [sip-comm-dev] Volunteers for
implementing JXTA support? 
>>>(was: jxta and addr
>>>Date: Tue, 25 Apr 2006 04:12:39 +0200
>>>
>>>Hello Nick,
>>>
>>>>Forgot to ask - when will the sip
audio/video be ready?
>>>It's hard to say. A month or two I guess.
>>>
>>>>...... hate to bring this up but .....
we're coming up to the
>>>>anniversary at the end of May of when
sip-communictor 1.0 with sip
>>>>audio/video should have originally been
ready .....
>>>Oh it was originally previewed for the end of
January 2005 so the 1 year
>>>anniversary has come and gone.
>>>We're doing what we can, and I think we're
already seeing the light at
>>>the end of the SIP Communicator crisis tunnel!
>>>
>>>>I'd be happy to do this once sip
audio/video are in place.
>>>Well, unless you have some other reason, you
don't really need to wait
>>>for them. All that's necessary to implement
JXTA instant messaging and
>>>presence is already there.
>>>
>>>Cheers
>>>Emil
>>>
>>>>>Cheers Nick
>>>>>
>>>>>
>>>>>>From: Emil Ivov <emil.ivovgmail.com> Reply-To:
>>>>>>devsip-communicator.dev.java.net To:
>>>>>>devsip-communicator.dev.java.net Subject: [sip-comm-dev]
>>>>>>Volunteers for implementing JXTA
support? (was: jxta and address
>>>>>>book) Date: Sun, 23 Apr 2006
06:16:31 +0200
>>>>>>
>>>>>>Hey Nick, all
>>>>>>
>>>>>>Took me a while huh . Well they
say - better late than never,
>>>>>>so here goes.
>>>>>>
>>>>>>buzz lightyear wrote:
>>>>>>>I just suddenly realised that
for jxta, a peerid is also needed
>>>>>>>for each peer. This is the ID
you use to contact another peer
>>>>>>>with.
>>>>>>All protocols in the SIP
Communicator are represented by the 
>>>>>>ProtocolProviderService package. The
package contains an
>>>>>>interface called ContactID. This
interface is implemented by the
>>>>>>various protocols in the way they
seem fit or in other words they
>>>>>>could just as well wrap the
implementation around a PeerID.
>>>>>>
>>>>>>Incidentally, I am using the
opportunity to ask whether someone
>>>>>>out there would be a volunteer to
start an implementation of the
>>>>>>  ProtocolProviderService over JXTA?
I personally think that this
>>>>>>would be a very cool thing to do!
>>>>>>
>>>>>>Don't be shy! Step forward!
>>>>>>
>>>>>>Cheers Emil
>>>>>>
>>>>>>
>>>>>>
>>>>>>------------------------------------
---------------------------------
>>>>>>  To unsubscribe, e-mail:
>>>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>>
>>>>>________________________________________
_________________________ Are 
>>>>>you using the latest version of MSN
Messenger? Download MSN
>>>>>Messenger 7.5 today! http://join.ms
n.com/messenger/overview
>>>>>
>>>>>----------------------------------------
-----------------------------
>>>>>  To unsubscribe, e-mail:
>>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>
>>>>____________________________________________
_____________________ Are
>>>>you using the latest version of MSN
Messenger? Download MSN Messenger
>>>>  7.5 today! http://join.ms
n.com/messenger/overview
>>>>
>>>>--------------------------------------------
-------------------------
>>>>  To unsubscribe, e-mail:
>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>
>>>>
>>>------------------------------------------------
---------------------
>>>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>
>>____________________________________________________
_____________
>>Express yourself instantly with MSN Messenger!
Download today - it's FREE! 
>>http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/
>>
>>----------------------------------------------------
-----------------
>>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
>
>--------------------------------------------------------
-------------
>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>

____________________________________________________________
_____
Be the first to hear what's new at MSN - sign up to our
free newsletters! 
http://www.msn.co.uk
/newsletters

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello Nick,

Glad to hear from you again.


There are basically two ways one would integrate jxta (or
any other 
protocol for that matter) in the sip communicator and each
of them is on 
a different level.

The ProtocolProviderService level is meant to offer a black
box 
interface to instant messaging and telephony destined for
high level 
bundles such as the GUI. A jxta implementation of this
service would 
therefore have to implement its own instant messaging  and
telephony 
routines (if any). Concurrent ProtocolProviderService
implementations 
_do_not_ refer to each other.

What you are talking about is a lower level that would be
exporting 
interfaces to all jxta specific stuff so that other
protocols would use 
it. Right now this is something we don't really need since
no other 
protocol provider is even close to using jxta and if some do
one day we 
have no idea which ones and how they'll be using it.

I saw on jxta.org that they have jxta specific instant
messaging. It 
would be nice if we could start there. In other words
implementing a 
jxta protocol provider that also implements the presence and
IM 
operation sets would be nice.

How does this sound?

Emil



buzz lightyear wrote:
> Apologies for not getting back sooner.
> 
> I've been thinking about the best approach for using
jxta within 
> sip-communicator and I'm beginning to favour some sort
of factory with which 
> protocols can register themselves and request
pipes/streams to be created 
> between peers - in the sip-communicator context, jxta
is acting as more of a 
> transport than a protocol to an external service (yes,
the protocol maybe 
> routed back to another sip-communicator).
> 
> The jxta protocol/transport will listen to, and
broadcast the presence 
> status, of the user, and also respond correctly
reflectin the users contact 
> list.
> 
> To recap, briefly, on jxta, peers communicate with each
other by initially 
> contacting a jxta rendezvous, discover other peers and
then talk directly 
> with each other. For those peers that are behind a hard
firewall, they need 
> to go through the firewall via a jxta relay.
> 
> Jxta  peers start in an initial peergroup and then can
create additional 
> peer groups, join the peergroups; create services in
any of the peergroups 
> and use the various services offered by other peers via
pipes - sockets or 
> messages (messages are xml, with subclasses of byte[]
and string).... and 
> sockets chunk everything into byte[] and use the pipes.
> 
> So, by offering a jxta factory by which sip, icq etc
have the freedom to 
> create any number of streams/pipes between peers and
their respective 
> protocols, this, surely, should be flexible enough?
> 
> I hope I'm going in the right direction here for
everyone?
> 
> I'm out for the whole of next week, but intend
devoting the following week 
> to writing a skeleton and commiting it (lgpl, of
course).
> 
> Cheers
> Nick
> 
> 
>> From: Emil Ivov <emil.ivovgmail.com>
>> Reply-To: devsip-communicator.dev.java.net
>> To: devsip-communicator.dev.java.net
>> Subject: Re: [sip-comm-dev] Volunteers for
implementing JXTA support? (was: 
>> jxta and addr
>> Date: Tue, 25 Apr 2006 14:39:43 +0200
>>
>> Hi Nick,
>>
>> buzz lightyear wrote:
>>> I'll put together a rough proposal and a
skeleton ProtocolProviderService 
>>> implementation over the next week or so.
>> Hey hey! Am I glad to hear that!
>>
>>> If someone is already working on the sip
audeo/video service then please 
>>> send me a mail - some thought needs to go into
the media and sip 
>>> streams/pipes/sockets etc
>> Will do Nick.
>>
>> Cheers
>> Emil
>>
>>> Cheers
>>> Nick
>>>
>>>> From: Emil Ivov <emil.ivovgmail.com>
>>>> Reply-To: devsip-communicator.dev.java.net
>>>> To: devsip-communicator.dev.java.net
>>>> Subject: Re: [sip-comm-dev] Volunteers for
implementing JXTA support? 
>>>> (was: jxta and addr
>>>> Date: Tue, 25 Apr 2006 04:12:39 +0200
>>>>
>>>> Hello Nick,
>>>>
>>>>> Forgot to ask - when will the sip
audio/video be ready?
>>>> It's hard to say. A month or two I guess.
>>>>
>>>>> ...... hate to bring this up but .....
we're coming up to the
>>>>> anniversary at the end of May of when
sip-communictor 1.0 with sip
>>>>> audio/video should have originally been
ready .....
>>>> Oh it was originally previewed for the end
of January 2005 so the 1 year
>>>> anniversary has come and gone.
>>>> We're doing what we can, and I think
we're already seeing the light at
>>>> the end of the SIP Communicator crisis
tunnel!
>>>>
>>>>> I'd be happy to do this once sip
audio/video are in place.
>>>> Well, unless you have some other reason,
you don't really need to wait
>>>> for them. All that's necessary to
implement JXTA instant messaging and
>>>> presence is already there.
>>>>
>>>> Cheers
>>>> Emil
>>>>
>>>>>> Cheers Nick
>>>>>>
>>>>>>
>>>>>>> From: Emil Ivov
<emil.ivovgmail.com> Reply-To:
>>>>>>> devsip-communicator.dev.java.net To:
>>>>>>> devsip-communicator.dev.java.net Subject: [sip-comm-dev]
>>>>>>> Volunteers for implementing
JXTA support? (was: jxta and address
>>>>>>> book) Date: Sun, 23 Apr 2006
06:16:31 +0200
>>>>>>>
>>>>>>> Hey Nick, all
>>>>>>>
>>>>>>> Took me a while huh . Well they
say - better late than never,
>>>>>>> so here goes.
>>>>>>>
>>>>>>> buzz lightyear wrote:
>>>>>>>> I just suddenly realised
that for jxta, a peerid is also needed
>>>>>>>> for each peer. This is the
ID you use to contact another peer
>>>>>>>> with.
>>>>>>> All protocols in the SIP
Communicator are represented by the 
>>>>>>> ProtocolProviderService
package. The package contains an
>>>>>>> interface called ContactID.
This interface is implemented by the
>>>>>>> various protocols in the way
they seem fit or in other words they
>>>>>>> could just as well wrap the
implementation around a PeerID.
>>>>>>>
>>>>>>> Incidentally, I am using the
opportunity to ask whether someone
>>>>>>> out there would be a volunteer
to start an implementation of the
>>>>>>>  ProtocolProviderService over
JXTA? I personally think that this
>>>>>>> would be a very cool thing to
do!
>>>>>>>
>>>>>>> Don't be shy! Step forward!
>>>>>>>
>>>>>>> Cheers Emil
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
------------------------------------------------------------
---------
>>>>>>>  To unsubscribe, e-mail:
>>>>>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>>>
>>>>>>
____________________________________________________________
_____ Are 
>>>>>> you using the latest version of MSN
Messenger? Download MSN
>>>>>> Messenger 7.5 today! http://join.ms
n.com/messenger/overview
>>>>>>
>>>>>>
------------------------------------------------------------
---------
>>>>>>  To unsubscribe, e-mail:
>>>>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>>
>>>>>
____________________________________________________________
_____ Are
>>>>> you using the latest version of MSN
Messenger? Download MSN Messenger
>>>>>  7.5 today! http://join.ms
n.com/messenger/overview
>>>>>
>>>>>
------------------------------------------------------------
---------
>>>>>  To unsubscribe, e-mail:
>>>>> dev-unsubscribesip-communicator.dev.java.net For additional
>>>>> commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>
>>>>>
>>>>
------------------------------------------------------------
---------
>>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>>> For additional commands, e-mail:
dev-helpsip-communicator.dev.java.net
>>>>
>>>
____________________________________________________________
_____
>>> Express yourself instantly with MSN Messenger!
Download today - it's FREE! 
>>> http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/
>>>
>>>
------------------------------------------------------------
---------
>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
> 
>
____________________________________________________________
_____
> Be the first to hear what's new at MSN - sign up to
our free newsletters! 
> http://www.msn.co.uk
/newsletters
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Emil

My interest really is with implementing standard protocols,
such as sip, 
over jxta. You can already use myjxta2 for video, audio and
messaging via 
jxta.

Sincere apologies for offering do this and now pull out, and
hope that 
sip-communicator really challenges skype!

Best of luck.

Cheers
Nick


>From: Emil Ivov <emil.ivovgmail.com>
>Reply-To: devsip-communicator.dev.java.net
>To: devsip-communicator.dev.java.net
>Subject: Re: [sip-comm-dev] Volunteers for implementing
JXTA support?
>Date: Fri, 12 May 2006 11:10:03 +0200
>
>Hello Nick,
>
>Glad to hear from you again.
>
>
>There are basically two ways one would integrate jxta
(or any other 
>protocol for that matter) in the sip communicator and
each of them is on a 
>different level.
>
>The ProtocolProviderService level is meant to offer a
black box interface 
>to instant messaging and telephony destined for high
level bundles such as 
>the GUI. A jxta implementation of this service would
therefore have to 
>implement its own instant messaging  and telephony
routines (if any). 
>Concurrent ProtocolProviderService implementations
_do_not_ refer to each 
>other.
>
>What you are talking about is a lower level that would
be exporting 
>interfaces to all jxta specific stuff so that other
protocols would use it. 
>Right now this is something we don't really need since
no other protocol 
>provider is even close to using jxta and if some do one
day we have no idea 
>which ones and how they'll be using it.
>
>I saw on jxta.org that they have jxta specific instant
messaging. It would 
>be nice if we could start there. In other words
implementing a jxta 
>protocol provider that also implements the presence and
IM operation sets 
>would be nice.
>
>How does this sound?
>
>Emil
>
>
>
>buzz lightyear wrote:
>>Apologies for not getting back sooner.
>>
>>I've been thinking about the best approach for
using jxta within 
>>sip-communicator and I'm beginning to favour some
sort of factory with 
>>which protocols can register themselves and request
pipes/streams to be 
>>created between peers - in the sip-communicator
context, jxta is acting as 
>>more of a transport than a protocol to an external
service (yes, the 
>>protocol maybe routed back to another
sip-communicator).
>>
>>The jxta protocol/transport will listen to, and
broadcast the presence 
>>status, of the user, and also respond correctly
reflectin the users 
>>contact list.
>>
>>To recap, briefly, on jxta, peers communicate with
each other by initially 
>>contacting a jxta rendezvous, discover other peers
and then talk directly 
>>with each other. For those peers that are behind a
hard firewall, they 
>>need to go through the firewall via a jxta relay.
>>
>>Jxta  peers start in an initial peergroup and then
can create additional 
>>peer groups, join the peergroups; create services in
any of the peergroups 
>>and use the various services offered by other peers
via pipes - sockets or 
>>messages (messages are xml, with subclasses of
byte[] and string).... and 
>>sockets chunk everything into byte[] and use the
pipes.
>>
>>So, by offering a jxta factory by which sip, icq etc
have the freedom to 
>>create any number of streams/pipes between peers and
their respective 
>>protocols, this, surely, should be flexible enough?
>>
>>I hope I'm going in the right direction here for
everyone?
>>
>>I'm out for the whole of next week, but intend
devoting the following week 
>>to writing a skeleton and commiting it (lgpl, of
course).
>>
>>Cheers
>>Nick
>>
>>
>>>From: Emil Ivov <emil.ivovgmail.com>
>>>Reply-To: devsip-communicator.dev.java.net
>>>To: devsip-communicator.dev.java.net
>>>Subject: Re: [sip-comm-dev] Volunteers for
implementing JXTA support? 
>>>(was: jxta and addr
>>>Date: Tue, 25 Apr 2006 14:39:43 +0200
>>>
>>>Hi Nick,
>>>
>>>buzz lightyear wrote:
>>>>I'll put together a rough proposal and a
skeleton 
>>>>ProtocolProviderService implementation over
the next week or so.
>>>Hey hey! Am I glad to hear that!
>>>
>>>>If someone is already working on the sip
audeo/video service then please 
>>>>send me a mail - some thought needs to go
into the media and sip 
>>>>streams/pipes/sockets etc
>>>Will do Nick.
>>>
>>>Cheers
>>>Emil
>>>
>>>>Cheers
>>>>Nick
>>>>
>>>>>From: Emil Ivov <emil.ivovgmail.com>
>>>>>Reply-To: devsip-communicator.dev.java.net
>>>>>To: devsip-communicator.dev.java.net
>>>>>Subject: Re: [sip-comm-dev] Volunteers
for implementing JXTA support? 
>>>>>(was: jxta and addr
>>>>>Date: Tue, 25 Apr 2006 04:12:39 +0200
>>>>>
>>>>>Hello Nick,
>>>>>
>>>>>>Forgot to ask - when will the sip
audio/video be ready?
>>>>>It's hard to say. A month or two I
guess.
>>>>>
>>>>>>...... hate to bring this up but
..... we're coming up to the
>>>>>>anniversary at the end of May of
when sip-communictor 1.0 with sip
>>>>>>audio/video should have originally
been ready .....
>>>>>Oh it was originally previewed for the
end of January 2005 so the 1 
>>>>>year
>>>>>anniversary has come and gone.
>>>>>We're doing what we can, and I think
we're already seeing the light at
>>>>>the end of the SIP Communicator crisis
tunnel!
>>>>>
>>>>>>I'd be happy to do this once sip
audio/video are in place.
>>>>>Well, unless you have some other reason,
you don't really need to wait
>>>>>for them. All that's necessary to
implement JXTA instant messaging and
>>>>>presence is already there.
>>>>>
>>>>>Cheers
>>>>>Emil
>>>>>
>>>>>>>Cheers Nick
>>>>>>>
>>>>>>>
>>>>>>>>From: Emil Ivov
<emil.ivovgmail.com> Reply-To:
>>>>>>>>devsip-communicator.dev.java.net To:
>>>>>>>>devsip-communicator.dev.java.net Subject: [sip-comm-dev]
>>>>>>>>Volunteers for implementing
JXTA support? (was: jxta and address
>>>>>>>>book) Date: Sun, 23 Apr 2006
06:16:31 +0200
>>>>>>>>
>>>>>>>>Hey Nick, all
>>>>>>>>
>>>>>>>>Took me a while huh . Well they
say - better late than never,
>>>>>>>>so here goes.
>>>>>>>>
>>>>>>>>buzz lightyear wrote:
>>>>>>>>>I just suddenly realised
that for jxta, a peerid is also needed
>>>>>>>>>for each peer. This is
the ID you use to contact another peer
>>>>>>>>>with.
>>>>>>>>All protocols in the SIP
Communicator are represented by the 
>>>>>>>>ProtocolProviderService
package. The package contains an
>>>>>>>>interface called ContactID.
This interface is implemented by the
>>>>>>>>various protocols in the way
they seem fit or in other words they
>>>>>>>>could just as well wrap the
implementation around a PeerID.
>>>>>>>>
>>>>>>>>Incidentally, I am using the
opportunity to ask whether someone
>>>>>>>>out there would be a
volunteer to start an implementation of the
>>>>>>>>  ProtocolProviderService
over JXTA? I personally think that this
>>>>>>>>would be a very cool thing
to do!
>>>>>>>>
>>>>>>>>Don't be shy! Step forward!
>>>>>>>>
>>>>>>>>Cheers Emil
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>----------------------------
-----------------------------------------
>>>>>>>>  To unsubscribe, e-mail:
>>>>>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>>>>commands, e-mail:
dev-helpsip-communicator.dev.java.net
>>>>>>>>
>>>>>>>________________________________
_________________________________ Are 
>>>>>>>you using the latest version of
MSN Messenger? Download MSN
>>>>>>>Messenger 7.5 today! http://join.ms
n.com/messenger/overview
>>>>>>>
>>>>>>>--------------------------------
-------------------------------------
>>>>>>>  To unsubscribe, e-mail:
>>>>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>>>
>>>>>>____________________________________
_____________________________ Are
>>>>>>you using the latest version of MSN
Messenger? Download MSN Messenger
>>>>>>  7.5 today! http://join.ms
n.com/messenger/overview
>>>>>>
>>>>>>------------------------------------
---------------------------------
>>>>>>  To unsubscribe, e-mail:
>>>>>>dev-unsubscribesip-communicator.dev.java.net For additional
>>>>>>commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>>>>
>>>>>>
>>>>>----------------------------------------
-----------------------------
>>>>>To unsubscribe, e-mail:
dev-unsubscribesip-communicator.dev.java.net
>>>>>For additional commands, e-mail:
dev-helpsip-communicator.dev.java.net
>>>>>
>>>>____________________________________________
_____________________
>>>>Express yourself instantly with MSN
Messenger! Download today - it's 
>>>>FREE! http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/
>>>>
>>>>--------------------------------------------
-------------------------
>>>>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>>>For additional commands, e-mail:
dev-helpsip-communicator.dev.java.net
>>>>
>>>>
>>>------------------------------------------------
---------------------
>>>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>
>>____________________________________________________
_____________
>>Be the first to hear what's new at MSN - sign up to
our free newsletters! 
>>http://www.msn.co.uk
/newsletters
>>
>>----------------------------------------------------
-----------------
>>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
>
>--------------------------------------------------------
-------------
>To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>

____________________________________________________________
_____
Be the first to hear what's new at MSN - sign up to our
free newsletters! 
http://www.msn.co.uk
/newsletters

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net