Volunteers for implementing JXTA support?

Hello Pedro,

Pedro Oliveira wrote:
> 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.

Well, if you no longer want to do MSN you are free to start
hacking on
jxta. That's what open source is about- anyone could hack
on whatever
they want. However I don't think either of them is less
important than
the other so MSN is also quite a very good opportunity for a
meaningful
contribution.

> 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!

All we really need is modify the classpath. I wonder whether
this could
be done by the taskdef or typedef tasks?

> 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!!!!

Cool,

> 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

Yes looks nice. Have you tried using the stacks that I sent
you a while
ago? Creating a new stack from scratch would be too much of
a
development and a maintenance burden. Besides you'd be able
to produce
something working much faster this way.

Cheers
Emil


> 
> 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
> 
> 

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

Hi Emil,

If it is one or another, I will keep with MSN.

I looked the MSN libraries sites, but i still have to look
the deeply!

Could you explain a little bit more your classpath
suggestion!!!

Thanks and regards
Pedro

Emil Ivov wrote:

> Hello Pedro,
>
> Pedro Oliveira wrote:
>
>> 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.
>
>
> Well, if you no longer want to do MSN you are free to
start hacking on
> jxta. That's what open source is about- anyone could
hack on whatever
> they want. However I don't think either of them is
less important than
> the other so MSN is also quite a very good opportunity
for a meaningful
> contribution.
>
>> 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!
>
>
> All we really need is modify the classpath. I wonder
whether this could
> be done by the taskdef or typedef tasks?
>
>> 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!!!!
>
>
> Cool,
>
>> 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
>
>
> Yes looks nice. Have you tried using the stacks that I
sent you a while
> ago? Creating a new stack from scratch would be too
much of a
> development and a maintenance burden. Besides you'd be
able to produce
> something working much faster this way.
>
> Cheers
> Emil
>
>
>>
>> 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
>>
>>
>
>
------------------------------------------------------------
---------
> 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

Hello Pedro,

>  Could you explain a little bit more your classpath
suggestion!!!

The only reason we need to launch ant from inside the
build.xml is 
because we need to modify the classpath of the VM that is
running ant 
itself and add xalan to it. If we find another way of
modifying this 
classpath, then we won't need to to launch ant at all. So I
was 
wondering whether using taskdef and typedef could do that
trick.

Emil

Pedro Oliveira wrote:
> Hi Emil,
> 
> If it is one or another, I will keep with MSN.
> 
> I looked the MSN libraries sites, but i still have to
look the deeply!
> 
> Could you explain a little bit more your classpath
suggestion!!!
> 
> Thanks and regards
> Pedro
> 
> Emil Ivov wrote:
> 
>> Hello Pedro,
>>
>> Pedro Oliveira wrote:
>>
>>> 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.
>>
>> Well, if you no longer want to do MSN you are free
to start hacking on
>> jxta. That's what open source is about- anyone
could hack on whatever
>> they want. However I don't think either of them is
less important than
>> the other so MSN is also quite a very good
opportunity for a meaningful
>> contribution.
>>
>>> 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!
>>
>> All we really need is modify the classpath. I
wonder whether this could
>> be done by the taskdef or typedef tasks?
>>
>>> 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!!!!
>>
>> Cool,
>>
>>> 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
>>
>> Yes looks nice. Have you tried using the stacks
that I sent you a while
>> ago? Creating a new stack from scratch would be too
much of a
>> development and a maintenance burden. Besides
you'd be able to produce
>> something working much faster this way.
>>
>> Cheers
>> Emil
>>
>>
>>> 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
>>>
>>>
>>
------------------------------------------------------------
---------
>> 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
> 
> 

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