Dynamic port assignment request for iViewer

8 views
Skip to first unread message

DO_PUSH

unread,
Jul 15, 2009, 11:38:15 AM7/15/09
to CommandFusion
I have been working on adapting the latest iViewer AMX module to our
standard programming for client use. The way iViewer works now is
one .gui file has one ip/port assigned to it. It seems that if the
iViewer protocol supported port assignment from the control system,
you could use one module and one .gui file for a large number of
iPhone connections in one system. I.e. iViewer contacts AMX or
Crestron on port 11 with an iViewer prot range from 11 to 21. Then the
control system sends back a string changing the iViewer to an open
port (12) and makes the UI connection there unitl it disconnects. When
the next iViewer connection comes into the control system it would
make a port assignment to 13 and so on. This way would allow all
iPhones on the system to connect on the same standard port and the
control system could manage the connections. This could be a very big
deal for control system programmers and built into the standard module
for AMX or Crestron. At this time, I don't think that Crestron's
iPhone app is even this efficient.

Jarrod

unread,
Jul 16, 2009, 2:50:58 AM7/16/09
to CommandFusion
This is something we actually have working for the upcoming webViewer
(still a few months off!).

I can't really see multiple iPhone/iPods running the same GUI very
often (unlike a web page being run multiple times at once) - not
enough to change a quite major part of the code anyway.

Its quite easy to duplicate a GUI project, change the IP address, and
throw all copies onto the built in web server of a control system and
serve the GUI files from there. You can edit GUI files in a text
editor for small changes like that. The format is quite easy to
understand (XML).

Jarrod

DO_PUSH

unread,
Jul 16, 2009, 7:19:38 PM7/16/09
to CommandFusion
I have been doing some more work on this. It seems that if the upload
of the .gui file were to be marshalled by the control system, the
control system module could allocate and rewrite the port in the file
before transmitting it. This would allow the feature set I described
above. It is very nice to have one UI file and be able to manipulate
it from code instead of having to build several different files. The
module could then control which port is hooked up to which UI in the
code. I will update with some code when I am finished with it. I am
currently working on the AMX module, but this could be done in
Crestron too.
> > iPhone app is even this efficient.- Hide quoted text -
>
> - Show quoted text -
Reply all
Reply to author
Forward
0 new messages