From ros-users-bounces@code.ros.org Wed Mar 30 17:14:43 2011 Return-Path: X-Original-To: www-data@code.ros.org Delivered-To: www-data@code.ros.org Received: from pub5.willowgarage.com (localhost [127.0.0.1]) by pub5.willowgarage.com (Postfix) with ESMTP id C7FF825C7E8; Wed, 30 Mar 2011 17:14:43 -0700 (PDT) X-Original-To: ros-users@code.ros.org Delivered-To: ros-users@code.ros.org Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by pub5.willowgarage.com (Postfix) with ESMTPS id A939225C13C for ; Wed, 30 Mar 2011 17:14:42 -0700 (PDT) Received: by wya21 with SMTP id 21so2039482wya.5 for ; Wed, 30 Mar 2011 17:14:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.28.217 with SMTP id n25mr1996884wbc.68.1301530480402; Wed, 30 Mar 2011 17:14:40 -0700 (PDT) Received: by 10.227.136.5 with HTTP; Wed, 30 Mar 2011 17:14:40 -0700 (PDT) Date: Wed, 30 Mar 2011 20:14:40 -0400 Message-ID: From: John Peabody Jr To: ros-users@code.ros.org Subject: [ros-users] ROSUDP in ROSPY X-BeenThere: ros-users@code.ros.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: User discussions List-Id: User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5519007180513900952==" Mime-version: 1.0 Sender: ros-users-bounces@code.ros.org Errors-To: ros-users-bounces@code.ros.org --===============5519007180513900952== Content-Type: multipart/alternative; boundary=002215b040b2f2e1d9049fbc2dfe --002215b040b2f2e1d9049fbc2dfe Content-Type: text/plain; charset=ISO-8859-1 Hi, I recently began a project that uses ROS and we are looking to leverage ROSPY. It is actually a ROS node on a mobile device so we are utilizing the great work done by the gentlemen at TUM ( http://www.ros.org/news/2011/02/rospy-on-android.html). The issue however, is that we would like to subscribe to topics using ROSUDP within ROSPY. We would rather have the ability to drop connection and have it come back on line quickly then attempt to guaranty delivery of every message. I have followed the tracker and previous posts on this list and it looks like the idea of developing ROSUDP for ROSPY is no longer of interest. Is this really the case? I would appreciate any guidance on this matter. John --002215b040b2f2e1d9049fbc2dfe Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I recently began a project that uses ROS and we are looking to l= everage ROSPY. It is actually a ROS node on a mobile device so we are utili= zing the great work done by the gentlemen at TUM (http://www.ros.org/news/2011/02/ro= spy-on-android.html).

The issue however, is that we would like to subscribe to topics using R= OSUDP within ROSPY. We would rather have the ability to drop connection and= have it come back on line quickly then attempt to guaranty delivery of eve= ry message. I have followed the tracker and previous posts on this list and= it looks like the idea of developing ROSUDP for ROSPY is no longer of inte= rest. Is this really the case?

I would appreciate any guidance on this matter.

John
--002215b040b2f2e1d9049fbc2dfe-- --===============5519007180513900952== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ros-users mailing list ros-users@code.ros.org https://code.ros.org/mailman/listinfo/ros-users --===============5519007180513900952==--