[Helma-user] Java File Upload Applet to Helma intergration

[Maksim Lin for technical support mailling lists]

Hi Julian,
 
Glad you solved your problem - sorry I couldnt be of more help, to be
honest I'm still more often confused then enlightened when it comes to
ipv6 problems.
 
its very generous of you to share your work with the applet, if you like
I can make an sftp account and some space on my server for it ?
 
But if you're interested, perhaps you could put it up as a new project
on http://code.google.com <BLOCKED::http://code.google.com>  ? all you
need is a gmail address to login and its a much, much simpler process to
make a new project then with sites like sourceforge...
I'd certainly be very intersted in this kind of generic upload app for
several of projects and would happy to conctribute back any extra
features I might add as open src.
 
Or if you prefer, you can upload the code to me vis sftp and then I can
setup a project with it on google code, if you are pressed for time?
 
 
 
Maks.

________________________________

From: helma-user-bounces at helma.org [mailto:helma-user-bounces at helma.org]
On Behalf Of Julian Tree
Sent: Wednesday, 16 August 2006 4:28 AM
To: Helma User Mailing List
Subject: Re: [Helma-user] Java File Upload Applet to Helma intergration



Thanks Stefan,  I end up developing using http://127.0.0.1:8080 URL, 
that seem to have solved the problem. Because I am on a DHCP, I don't 
want to change my host file everytime it gets a new one.

However it is very odd that the Mac or Java or Mac DNS resolution 
works that way,

Even if I took out the name from the v6 ip such as below
127.0.0.1       localhost filepress.local  255.255.255.255 broadcasthost
::1             localhost

Notice filepress.local is not in the v6 mapping, but  when I hit
        http://filepress.local:8080, I will get 127.0.0.1 IP for a
while, 
but eventually it falls back to the 0.0.0.0.0.0 IP.  The only way to 
avoid that is to comment out the v6 IP entry in the /etc/hosts file  
completely.  I guess it is good forward compatibility thinking.

But, I have the modified gallery_remote code ready, but it is around 
16mb, gmail only support up to 10mb.  So if anyone wants it let me 
know maybe we can send over im or something.


On Aug 15, 2006, at 3:10 AM, Stefan Rinner wrote:

>> When the browser first hit helma the http_remotehost is reconized as
>> http_remotehost=0:0:0:0:0:0:0:1%0
>>
>> but when the the Applet hits the server the server sees the remote
>> host as
>>  http_remotehost=127.0.0.1
>>
>> That ip address is then append to the session.cookie I assume.
>>
>> This cause a problem, because it views the applet and the web page as
>> two different sessions.
>
> I experienced similar problems and my workaround was not to use the
> loopback IP-adress, but the one your machine got in the network, then
> it works fine
>
> - stefan
> _______________________________________________
> Helma-user mailing list
> Helma-user at helma.org
> http://helma.org/mailman/listinfo/helma-user

_______________________________________________
Helma-user mailing list
Helma-user at helma.org
http://helma.org/mailman/listinfo/helma-user


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://helma.org/pipermail/helma-user/attachments/20060816/75853973/attachment.html