applet name
Posted: Sat Jul 17, 2004 10:47 am
first, thanks for making such a great software so freely available! I really like it.
I'm not sure, but I think this is the issue I'm facing: the applet name - YawApplet.class (and also the jar file name, of course) - is too long to put in the text field to trigger the port on my router. very odd that the text field is limited in character length!
anyway, I am behind a Linksys router, using win98se, and I'm trying to stream via a page on my website. the html code on my page is for the signed applet, using the forced public ip. I can see my cam on the 'signed_example.html' Yawcam page (with the internal IP), but not on the page I've got on my website. I've enabled everything I can in the router setup, but it's just that trigger port that I can't do anything with that seems to be absolutely needed.
I've streamed my cam with the Hcam software on the same webpage before, by the way, and it worked... but then the applet name 'Hcam.class' easily fit into the trigger port text field!
very strange problem. any suggestions for me??
I'm not sure, but I think this is the issue I'm facing: the applet name - YawApplet.class (and also the jar file name, of course) - is too long to put in the text field to trigger the port on my router. very odd that the text field is limited in character length!
anyway, I am behind a Linksys router, using win98se, and I'm trying to stream via a page on my website. the html code on my page is for the signed applet, using the forced public ip. I can see my cam on the 'signed_example.html' Yawcam page (with the internal IP), but not on the page I've got on my website. I've enabled everything I can in the router setup, but it's just that trigger port that I can't do anything with that seems to be absolutely needed.
I've streamed my cam with the Hcam software on the same webpage before, by the way, and it worked... but then the applet name 'Hcam.class' easily fit into the trigger port text field!
very strange problem. any suggestions for me??