Closed GoogleCodeExporter closed 9 years ago
I took a look at your project when I was searching for upnp libraries, but I
couldn't find a quick example of how to do port forwarding and upnplib had a
"NAT mappings" link right in its Documentation page. So I chose upnplib.
Since I don't have one of these samsung TVs, I wouldn't be able to test the
code to support it, so it would be great if you could provide a patch with an
implementation of this feature. You can write a new NotificationReceiver like
UpnpNotificationReceiver. We can use your library instead of upnplib if it has
the same level of support that upnplib has for port forwarding.
Original comment by lehph...@gmail.com
on 14 Oct 2010 at 1:48
Please don't do this, specially not on the desktop client.
Me and someone else are already working on it as a separate app.
Original comment by rdamazio@gmail.com
on 14 Oct 2010 at 6:03
Just to clarify:
- IMHO new notification protocols/methods belong on the android side, they shouldn't depend on a desktop app.
- There's a queue of new methods to be implemented: GTalk, MSN, Samsung, etc. -
some of them may be implemented separately from the app (I have a pluggable
design in mind since some people asked me for very uncommon methods which don't
make sense to put in the main app)
- I do have a Samsung TV with such support (Samsung PL50C7000, 50-inch 3D
plasma which runs Linux), and I've done some initial experiments with it and
I've found out it's *not* as trivial as it sounds - I need to try your library,
but 99% of the other libraries I tried failed on that TV with a 403 HTTP error
- on the other side, they used the MessageBoxService SOAP call on the TV, which
afaik is not UPnP.
- All that said, I do want this support, so it will be done, but let's do it
right.
Original comment by rdamazio@gmail.com
on 14 Oct 2010 at 6:13
If libraries have already been ported to android, great, if not, then it's
faster to implement them in the desktop app, have people try them and if
everything works as expected, port to the android app.
I don't think it's better to have everything in the android app, some things
like support for Samsung TVs would make more sense in the desktop since the TV
will probably be in the home network only, other things like XMPP could make
more sense in the android app because it would work everywhere but more
features in the android app will make it harder for users to find what really
matters which is notification configuration only.
Original comment by lehph...@gmail.com
on 14 Oct 2010 at 6:49
Leandro, IMHO we shouldn't do what's faster - we should do what's better,
specially in cases where it means having duplicate work. Also, "porting to
android" is something very vague - any java-only code can be directly used in
Android (you may need to include a few additional dependencies, but it works).
About the TV specifically - I don't think having an additional relay hop makes
sense, it's an additional potential point of failure, plus it requires you to
keep a computer on.
About usability - that's why I'm proposing having that functionality outside
the main app.
Btw, I posted a document outlining what I believe should be the general
responsibility distribution:
http://code.google.com/p/android-notifier/wiki/MasterPlan
Perhaps we should continue this discussion on the google group?
Original comment by rdamazio@gmail.com
on 14 Oct 2010 at 7:05
Unfortunately, Android does not support everything in JavaSE, so we'll have to
port almost every library we decide to use for MSN, XMPP, UPNP etc. I think we
should do what is faster because libraries I've found for MSN and XMPP are far
from reliable and have varying degrees of compatibility, it would very
frustrating to port them to android to discover a large part of the users won't
be able to use the new features. Besides, many users don't have wifi available
and are using bluetooth or would like to use usb to get notifications to their
PC which may have a wired connection to the internet or a network router
allowing other forms of notification propagation.
I'm curious about having functionality outside the main app.
Original comment by lehph...@gmail.com
on 14 Oct 2010 at 7:19
New release of Cling, now with manual chapters for NAT port mapping and Samsung
TV messaging:
http://www.teleal.org/projects/cling/support/manual/cling-support-manual.html
http://www.teleal.org/projects/cling/core/manual/cling-core-manual.html
All of this works on Android or regular JVM.
Original comment by christia...@gmail.com
on 3 Nov 2010 at 2:09
As was in 94-2001 Saturn kia GM manual to help stop y2k terrist abyss mind
reading computer virus that attches to peoples pins and rods in body. Proper
fluids and amounts in car. 1AAA battery in oil, 1AAA battery in coolant, 2AAA
batteries in windshield washer fluids. Plug car into houses, buildings,
hospitals, anywhere and everywhere can and start am fm radios on and change
stations. Leave running, keep changing stations. When unplug and drive prevent
from overheating. Get as many people doing those methods with sat radio and
tune into Calgary Alberta radio station and doing methods in Calgary Alberta
Canada cause is targeted cause Greatest outdoor show on earth.
Original comment by doll7...@gmail.com
on 19 Dec 2013 at 9:35
Original issue reported on code.google.com by
christia...@gmail.com
on 14 Oct 2010 at 10:14