baljeetverma / android-notifier

Automatically exported from code.google.com/p/android-notifier
0 stars 0 forks source link

Multiple isolated instances with multiple concurrent windows users. #249

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,

I have enjoyed using this great program for a couple of weeks. But now that my 
girlfriend got her phone back from repair and I was looking forward to install 
the program on her user account on our main computer I realized that this was 
not at all possible since the program binds itself to the port.

This is my typical situation/usecase.

Main pc in living room turned on 24/7.
Admin windows account (mine) is always logged in and receives notifications 
from my android phone via internet and pushes them to a local running growl 
client which also receives and pushes notifications to and from another growl 
client running at my job workstation via a hamachi network.

I usually don't use the living room pc physically, but uses it a lot via remote 
desktop by logging in to my running session.

My girlfriend however, is using her own windows account on the same machine 
most of the day. This works really really great, but thats another story.

And so far so good...

But what I would love to be able to do is to run another instance of android 
notifier in her session so she will be able to receive notifications from her 
phone just like I do.

I was glad that the settings seemed to be stored per user and also the 
filtering of devices seemed useful, but it really doesn't work at all for me 
and I am unable to receive any test notification when I send it from her phone. 
The log however explains it all because theres a bind error when her android 
notifier client launches on login.

I guess I'm stuck for now...

Regards,
Mads

Original issue reported on code.google.com by madssand...@gmail.com on 19 Oct 2010 at 9:44

GoogleCodeExporter commented 9 years ago
In part this is a duplicate of issue 36, except I didn't really address the 
port customization there.
Leandro, is there anything that blocks the desktop app from having multiple 
instances?

Original comment by rdamazio@gmail.com on 19 Oct 2010 at 10:04

GoogleCodeExporter commented 9 years ago
The operating system does not allow two programs to bind to the same TCP port 
as you saw in the log file. But, you can run two instances and get 
notifications using UDP, select "Global broadcast address" in "Target IP 
Address" and keep "Send with UDP" checked in the android app.

Original comment by lehph...@gmail.com on 20 Oct 2010 at 12:08

GoogleCodeExporter commented 9 years ago
You are right, I can do that. But then the notifications can't be send via the 
cell network which is what I prefer. I'm interested in keeping our notification 
history even when we are on the go and not connected to any wifi.

Original comment by madssand...@gmail.com on 20 Oct 2010 at 12:40

GoogleCodeExporter commented 9 years ago
Maybe the port could be configurable per device.

Original comment by madssand...@gmail.com on 20 Oct 2010 at 12:41

GoogleCodeExporter commented 9 years ago
I think Rodrigo said we don't want to complicate things with configuration per 
device.

You can't just install the desktop app in your workstation at work? Usb support 
is being tested in issue 162 if don't have wifi at work.

Original comment by lehph...@gmail.com on 20 Oct 2010 at 1:26

GoogleCodeExporter commented 9 years ago
So, in general I'm in favor of keeping things simple, but I'm willing to 
address requests if enough users want it (as I did for having multiple IPs). 
Anyway, for now my top priority is getting commands ready and released, but 
after that I'll go back to addressing smaller requests, then I'll revisit 
setting custom ports.

Original comment by rdamazio@gmail.com on 20 Oct 2010 at 1:43

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
"...install the desktop app in your workstation at work...".

I could, I could, and I had until I discovered the send via cell network 
option. And we have wifi at work too, no static ip's though, so I would have to 
use broadcast and luckily notifications can be encrypted and is device specific 
since I'm not the only one using it at work. But what I want is to keep the 
notification history in growl, so notifications needs to be sent to something 
online 24/7 which is reachable even if i'm not at home or work.

Original comment by madssand...@gmail.com on 20 Oct 2010 at 10:36

GoogleCodeExporter commented 9 years ago
Just one comment about wifi without static IPs - if your wifi network does 
proper DNS (e.g. with DNSmasq), you can input hostnames instead of IPs.

Original comment by rdamazio@gmail.com on 20 Oct 2010 at 10:50

GoogleCodeExporter commented 9 years ago
Well, you could run the desktop app in a virtual machine at home so port 10600 
would be free for another instance of it running in the physical machine, but 
that's overkill, configurable TCP port would be better indeed. Perhaps a web 
site like suggested in issue 156 could keep a notification history too.

Original comment by lehph...@gmail.com on 21 Oct 2010 at 12:30

GoogleCodeExporter commented 9 years ago
Let's implement configurable ports by accepting that IPs or hostnames end with 
:12345 to indicate a port.

Original comment by rdamazio@gmail.com on 21 Oct 2010 at 4:39