Restlet and SIP

2010-11-18 Thread webpost 
All,

I am engaged in a VOIP project for which I would very much like to have a GWT 
SIP client.  Today, I noticed that the Restlet road map has identitified a SIP 
client to be ready Q2 2011.  I need this. My questions are simple.  Can I be of 
any help? and if so how?

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2682838

RE: Strange failure

2010-11-18 Thread Jerome Louvel 
Hi Richard,

Do you still encounter this issue with version 2.0.3? If so, could you enter a 
bug report? 

Also, have you tried an alternate connector like Jetty or Simple?

Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.o​rg
Noelios Technologies ~ http://www.noelios.com



-Message d'origine-
De : Richard Cole [mailto:richcol...@googlemail.com] 
Envoyé : jeudi 12 août 2010 16:57
À : discuss@restlet.tigris.org
Objet : RE: Strange failure

I have managed to grab a thread dump as the issue occurs:

restlet-24193...@4593 daemon, priority=5, in group 'main', status: 'RUNNING'
  at java.net.SocketInputStream.socketRead0(SocketInputStream.java:-1)
  at java.net.SocketInputStream.read(SocketInputStream.java:129)
  at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
  at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
  at 
org.restlet.engine.http.connector.ServerConnection.readMessage(ServerConnection.java:161)
  at 
org.restlet.engine.http.connector.Connection.readMessages(Connection.java:682)
  at 
org.restlet.engine.http.connector.Controller$2.run(Controller.java:95)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  at java.lang.Thread.run(Thread.java:595)

restlet-27981...@4586 daemon, priority=5, in group 'main', status: 'RUNNING'
  at org.restlet.engine.log.LogFilter.afterHandle(LogFilter.java:112)
  at org.restlet.routing.Filter.handle(Filter.java:205)
  at org.restlet.engine.ChainHelper.handle(ChainHelper.java:111)
  at org.restlet.Component.handle(Component.java:390)
  at org.restlet.Server.handle(Server.java:474)
  at 
org.restlet.engine.http.connector.BaseServerHelper.handle(BaseServerHelper.java:158)
  at 
org.restlet.engine.http.connector.BaseServerHelper.handleInbound(BaseServerHelper.java:167)
  at 
org.restlet.engine.http.connector.BaseHelper.handleNextInbound(BaseHelper.java:418)
  at 
org.restlet.engine.http.connector.Connection.readMessages(Connection.java:705)
  at 
org.restlet.engine.http.connector.Controller$2.run(Controller.java:95)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  at java.lang.Thread.run(Thread.java:595)

restlet-21985...@2258 daemon, priority=5, in group 'main', status: 'WAIT'
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:146)
  at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:807)
  at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1,122)
  at 
java.util.concurrent.SynchronousQueue$Node.waitForPut(SynchronousQueue.java:291)
  at 
java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:443)
  at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:475)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
  at java.lang.Thread.run(Thread.java:595)

restlet-11595...@2186, priority=5, in group 'main', status: 'RUNNING'
  at java.net.PlainSocketImpl.socketAccept(PlainSocketImpl.java:-1)
  at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
  at java.net.ServerSocket.implAccept(ServerSocket.java:450)
  at java.net.ServerSocket.accept(ServerSocket.java:421)
  at org.restlet.engine.http.connector.Acceptor.run(Acceptor.java:91)
  at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
  at java.util.concurrent.FutureTask.run(FutureTask.java:123)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  at java.lang.Thread.run(Thread.java:595)

restlet-6588...@2256 daemon, priority=5, in group 'main', status: 'RUNNING'
  at java.lang.Thread.sleep(Thread.java:-1)
  at 
org.restlet.engine.http.connector.Controller.run(Controller.java:250)
  at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
  at java.util.concurrent.FutureTask.run(FutureTask.java:123)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  at

RE: Intermittent Errors

2010-11-18 Thread Jerome Louvel 
Hi Fraser,

Do you still encounter issues in 2.0.3 which is now the stable version of the 
Restlet Framework? 

Also, 2.1 M1 is the new testing release and contains a much better performing 
internal HTTP connector.

Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.o​rg
Noelios Technologies ~ http://www.noelios.com



-Message d'origine-
De : webp...@tigris.org [mailto:webp...@tigris.org] 
Envoyé : lundi 30 août 2010 15:38
À : discuss@restlet.tigris.org
Objet : RE: Intermittent Errors

Update:

I switched form the 2.0.0 (stable) version to the latest snapshot, and things 
seem somewhat improved.

I was seeing quite a lot of NPE's usually trying to access the request entity 
and also a lot of socket timeouts, but after 50+ tests I only had one socket 
timeout failure (previously I would get a failure after small number of tests 
( 10), so at least things are heading in the right direction.

Looking forward to the next stable release (2.1 ?)

Regards

Fraser

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2653109

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2682864

Re: Content negotiation problem when using a specific server connector (Jetty, Simple or Netty)

2010-11-18 Thread David Fogel 
Hi Bruno, Thierry-

FYI, I just posted about an issue related to this one on the code list:

http://restlet.tigris.org/ds/viewMessage.do?dsForumId=7458dsMessageId=2682868

-Dave Fogel


On Fri, Aug 13, 2010 at 3:04 PM, Thierry Boileau
thierry.boil...@noelios.com wrote:
 Hello Bruno,

 thanks for reporting this issue. I've fixed it in the svn repository.

 Best regards,
 Thierry Boileau

 --
 http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2646537


--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2682870

RE: Restlet and SIP

2010-11-18 Thread Jerome Louvel 
Hi there,

I have just moved the SIP extension out of the incubator into the main modules 
so it ships with the next 2.1 M2 version due by the end of the year. It relies 
on the new internal HTTP/NIO connector which offers greater scalability and 
lower latency.

However, I'm wondering what you want to achieve with a GWT SIP client. GWT runs 
inside web browsers and are limited to the HTTP protocol. Could you elaborate a 
little more?

Otherwise, we will soon be looking for testers. For now if you can give us 
feed-back on this specification document that would be nice:
http://wiki.restlet.org/developers/257-restlet/300-restlet.html

Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.o​rg
Noelios Technologies ~ http://www.noelios.com




-Message d'origine-
De : webp...@tigris.org [mailto:webp...@tigris.org] 
Envoyé : jeudi 18 novembre 2010 21:55
À : discuss@restlet.tigris.org
Objet : Restlet and SIP

All,

I am engaged in a VOIP project for which I would very much like to have a GWT 
SIP client.  Today, I noticed that the Restlet road map has identitified a SIP 
client to be ready Q2 2011.  I need this. My questions are simple.  Can I be of 
any help? and if so how?

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2682838

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2682875

RE: Can not access wiki..

2010-11-18 Thread Thierry Boileau 
Hello Nick,

thanks for your report. I've tested Opera under Xubuntu and it fails too...
I'll keep you informed.

Best regards,
Thierry Boileau

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2683020