Skip to main content

3pcc example app - status update

5 replies [Last post]
jamattsson
Offline
Joined: 2005-12-05

Hi!

Finally, here it is - the status update on the 3pcc example app!

Included in this second release are web service support (over ParlayX), improved exception handling, extended documentation and a cleaner state sharing mechanism.

I've committed the new code to CVS and I've also updated the wiki page! Check it out at http://wiki.java.net/bin/view/Communications/3pccExample !

We hope you'll appreciate these new features!
And please, gives us feedback on our contribution!

200 - BYE
Jacob

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
ivelin
Offline
Joined: 2003-07-13

Nice work.

A few comments:
- showing usage mbeans is a very good idea. This is an undervalued JSLEE feature.
- thanks to PTI for the Parlay-X code. Important show case.
- Walkaround code on the wiki has some commented out snippets which are confusing
- The JSLEE SIP Proxy service should be fixed to reduce the complexity of the demo. SER should be still left as an option demonstrating interoperability with remote SIP Routers. Please open an issue about this problem or point to an existing one.
- state sharing via JNDI is rightfully pointed out as a hack. What alternatives do you have in mind?

> 200 - BYE

:)

niklasuhrberg
Offline
Joined: 2004-11-02

> - Walkaround code on the wiki has some commented out
> snippets which are confusing

Fixed

> - state sharing via JNDI is rightfully pointed out as
> a hack. What alternatives do you have in mind?

This was changed some time ago with the StateCallback interface, it's just that I didn't update the Wiki on this.
Fixed now!

ivelin
Offline
Joined: 2003-07-13

> > - state sharing via JNDI is rightfully pointed out
> as
> > a hack. What alternatives do you have in mind?
>
> This was changed some time ago with the StateCallback
> interface, it's just that I didn't update the Wiki on
> this.
> Fixed now!

I thought there are 2 state sharing issues. One was between the Web Layer and JSLEE. Ths StateCallback was a good solution for this case.
The other state sharing need was between 3pcc and SIP Sbbs. I still see code that uses a global cache to implement this.

niklasuhrberg
Offline
Joined: 2004-11-02

> I thought there are 2 state sharing issues. One was
> between the Web Layer and JSLEE. Ths StateCallback
> was a good solution for this case.
> The other state sharing need was between 3pcc and SIP
> Sbbs. I still see code that uses a global cache to
> implement this.

OK, a slight misunderstanding about what is meant by "state sharing" in this app.

You are absolutely right about the use of JNDI in a global cache which is also a hack.
This will be replaced when we have a Dialog activity, then there will be no need for any kind of cache.

The best way of implementing the dialog tracking functionality without a Dialog activity is, I think, by using the facility for named activity contexts.

We didn't bother rewriting this after it became clear that a Dialog activity is a natural enhancement of the SIP RA Type but admittedly it's a little frustrating that we didn't know about the named activity context facility from the beginning. Then the application would have used it...

ivelin
Offline
Joined: 2003-07-13

now it all makes sense again :)