state of milton bug status and stability.\

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

state of milton bug status and stability.\

hank williams
I was looking at the compatibility list here:


In looking at the list it seems as though there are a fair number of problems. Windows 7 isn't listed at all, and there seem to be problems with every version of windows listed. Are these milton problem, or would you say that windows just doesnt support webdav successfully. I guess I am wondering if the problems listed happen with other webdav servers or just windows.

On the mac front, I guess the question is the same. Are the mac's problems issues with *any* webdav server or just milton based webdav servers.

Thanks,

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Daniel Lichtenberger
FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7. Things
to keep in mind:
* Microsoft decided some years ago to disable basic authentication over
HTTP since it's totally insecure
* I think that I never got old http:// mapping for WebDAV working.

So, for example, the following URL format should work with "Connect
network drive":
\\<my-pc-name>@SSL\my-webdav-share

Note that "localhost" or the IP address don't seem to work in this case,
however, you can specify a port number after @SSL, as in:
\\my-pc@SSL:8443\...

Cheers,
Daniel

hank williams wrote:

> I was looking at the compatibility list here:
>
> http://milton.ettrema.com/compat/index.html
>
> In looking at the list it seems as though there are a fair number of
> problems. Windows 7 isn't listed at all, and there seem to be problems
> with every version of windows listed. Are these milton problem, or
> would you say that windows just doesnt support webdav successfully. I
> guess I am wondering if the problems listed happen with other webdav
> servers or just windows.
>
> On the mac front, I guess the question is the same. Are the mac's
> problems issues with *any* webdav server or just milton based webdav
> servers.
>
> Thanks,
> Hank
>
> --
> blog: whydoeseverythingsuck.com <http://whydoeseverythingsuck.com>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Milton-users mailing list
> [hidden email]
> http://lists.justthe.net/mailman/listinfo/milton-users
>  

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

hank williams
Thanks Daniel.

This is a little off topic from my core question about how stable milton is, but your comments do bring up some questions. I am new to webdav and am not quite clear on the format you are suggesting.

When you say the proper format is: "\\<my-pc-name>@SSL\my-webdav-share"

I really dont know what that means. If I have a webdav server at "somedomain.com" are you saying you need to type "\\<my-pc-name>@SSL\somedomain.com"?

And if so are you saying you need to put the port number before the domain like "\\<my-pc-name>@SSL:8443\somedomain.com" as opposed to after the domain, which is the usual standard?

And finally, why would you specify "<my-pc-name>" at all. I am presuming here that <my-pc-name> is the name of the client you are currently on, which is a strange thing to need to specify for an http based protocol. If I go to google I dont need to specify "http://<my-pc-name>@google.com" since the name of the local machine is somewhat irrelevant.

Thanks
Hank

On Thu, May 20, 2010 at 3:59 AM, Daniel Lichtenberger <[hidden email]> wrote:
FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7. Things
to keep in mind:
* Microsoft decided some years ago to disable basic authentication over
HTTP since it's totally insecure
* I think that I never got old http:// mapping for WebDAV working.

So, for example, the following URL format should work with "Connect
network drive":
\\<my-pc-name>@SSL\my-webdav-share

Note that "localhost" or the IP address don't seem to work in this case,
however, you can specify a port number after @SSL, as in:
\\my-pc@SSL:8443\...

Cheers,
Daniel

hank williams wrote:
> I was looking at the compatibility list here:
>
> http://milton.ettrema.com/compat/index.html
>
> In looking at the list it seems as though there are a fair number of
> problems. Windows 7 isn't listed at all, and there seem to be problems
> with every version of windows listed. Are these milton problem, or
> would you say that windows just doesnt support webdav successfully. I
> guess I am wondering if the problems listed happen with other webdav
> servers or just windows.
>
> On the mac front, I guess the question is the same. Are the mac's
> problems issues with *any* webdav server or just milton based webdav
> servers.
>
> Thanks,
> Hank
>
> --
> blog: whydoeseverythingsuck.com <http://whydoeseverythingsuck.com>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Milton-users mailing list
> [hidden email]
> http://lists.justthe.net/mailman/listinfo/milton-users
>




--
blog: whydoeseverythingsuck.com

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Øyvind Harboe
In reply to this post by Daniel Lichtenberger
I've been trying to use Milton and I've gotten the filesystem and test
application up and running.

I've got concerns in two areas:

- There are lots of tricks and tips on how to get WebDAV to work on various
versions of Windows and Office/OpenOffice, Linux, etc. I'm concerned that
users of our application won't succeed even if the reset works perfectly.
I suppose this is just a generic concern about how well WebDAV works
in real-life situations. Untrained, impatient, disappointed, unmotivated
and angry users looking for an excuse not to use an application  + quirks
is not a good combination. :-)

- The stability of Milton itself. I think it would be great to have a
scaled down
and robust "hello world" example where I can verify that Office / OpenOffice
can open/create/re-save files and have locking working prooperly. The
milton-test and milton-filserver-test is perhaps too advanced? Perhaps this
boils down to a documentation issue where I'm having problems getting a
handle on WebDAV & Milton at the same time(being a newbie at both...)


--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by hank williams
Hi Hank,

I think Daniel was referring to using windows drive mapping to connect to a webdav server (ie from the command line) where my-pc-name is just the machine name running milton, usually the local machine for developers.

This particular MS dav client (there are several!) requires a windows UNC style address with the syntax given below. And Daniel's right, you can't access a server on localhost or 127.0.0.1, for some reason, it has to be a machine name. But if you just want to play around I suggest you stick with the "Add Network Location" feature because it doesnt worry about basic authentication over plain http. When it comes time to do a how-to page for your users/customers you can give some thought to what is the best mechanism for them to connect. The map drive has many advantages over the network place, but also has more restrictions.

Note that in most clients you specify webdav mount point as a regular http address, (which includes the windows "Add Network Location" feature), but Gnome's Nautilus is also a bit odd, you must use DAV:// instead of <a class="moz-txt-link-freetext" href="http://">http://

Cheers,
Brad

hank williams wrote:
Thanks Daniel.

This is a little off topic from my core question about how stable milton is, but your comments do bring up some questions. I am new to webdav and am not quite clear on the format you are suggesting.

When you say the proper format is: "\\<my-pc-name>@SSL\my-webdav-share"

I really dont know what that means. If I have a webdav server at "somedomain.com" are you saying you need to type "\\<my-pc-name>@SSL\somedomain.com"?

And if so are you saying you need to put the port number before the domain like "\\<my-pc-name>@SSL:8443\somedomain.com" as opposed to after the domain, which is the usual standard?

And finally, why would you specify "<my-pc-name>" at all. I am presuming here that <my-pc-name> is the name of the client you are currently on, which is a strange thing to need to specify for an http based protocol. If I go to google I dont need to specify "<a class="moz-txt-link-freetext" href="http://">http://<my-pc-name>@google.com" since the name of the local machine is somewhat irrelevant.

Thanks
Hank

On Thu, May 20, 2010 at 3:59 AM, Daniel Lichtenberger <[hidden email]> wrote:
FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7. Things
to keep in mind:
* Microsoft decided some years ago to disable basic authentication over
HTTP since it's totally insecure
* I think that I never got old <a class="moz-txt-link-freetext" href="http://">http:// mapping for WebDAV working.

So, for example, the following URL format should work with "Connect
network drive":
\\<my-pc-name>@SSL\my-webdav-share

Note that "localhost" or the IP address don't seem to work in this case,
however, you can specify a port number after @SSL, as in:
\\my-pc@SSL:8443\...

Cheers,
Daniel

hank williams wrote:
> I was looking at the compatibility list here:
>
> http://milton.ettrema.com/compat/index.html
>
> In looking at the list it seems as though there are a fair number of
> problems. Windows 7 isn't listed at all, and there seem to be problems
> with every version of windows listed. Are these milton problem, or
> would you say that windows just doesnt support webdav successfully. I
> guess I am wondering if the problems listed happen with other webdav
> servers or just windows.
>
> On the mac front, I guess the question is the same. Are the mac's
> problems issues with *any* webdav server or just milton based webdav
> servers.
>
> Thanks,
> Hank
>
> --
> blog: whydoeseverythingsuck.com <http://whydoeseverythingsuck.com>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Milton-users mailing list
> [hidden email]
> http://lists.justthe.net/mailman/listinfo/milton-users
>




--
blog: whydoeseverythingsuck.com
_______________________________________________ Milton-users mailing list [hidden email] http://lists.justthe.net/mailman/listinfo/milton-users


_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Øyvind Harboe
I think with a correctly implemented milton server its only
windows-vista which has useability problems. The one thing which has
been an achilles heal for milton for most of its life was poor locking
which affected office, open office and mac clients. But thats sorted now
so they should work out of the box.

Windows Vista has a problem with the "Add network location" feature
where folder browsing just doesnt work properly - double clicking a
folder just doesnt do anything, you have to navigate from the left pane
or address bar dropdown. But now that milton has Digest authentication
support you should be able to use drive mapping instead which (i think)
doesnt have that problem.

milton-test is intended to be a minimal implementation, while
milton-filesystem-test adds some bells and whistles such as FTP and the
web console. Is there something you can suggest to make milton-test
simpler? Note that the series of tutorials i've started on are be
absolutely minimal
(http://milton.ettrema.com/guide/tutorials/hibernate/index.html) and
should help the learning curve.

Øyvind Harboe wrote:

> I've been trying to use Milton and I've gotten the filesystem and test
> application up and running.
>
> I've got concerns in two areas:
>
> - There are lots of tricks and tips on how to get WebDAV to work on various
> versions of Windows and Office/OpenOffice, Linux, etc. I'm concerned that
> users of our application won't succeed even if the reset works perfectly.
> I suppose this is just a generic concern about how well WebDAV works
> in real-life situations. Untrained, impatient, disappointed, unmotivated
> and angry users looking for an excuse not to use an application  + quirks
> is not a good combination. :-)
>
> - The stability of Milton itself. I think it would be great to have a
> scaled down
> and robust "hello world" example where I can verify that Office / OpenOffice
> can open/create/re-save files and have locking working prooperly. The
> milton-test and milton-filserver-test is perhaps too advanced? Perhaps this
> boils down to a documentation issue where I'm having problems getting a
> handle on WebDAV&  Milton at the same time(being a newbie at both...)
>
>
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Øyvind Harboe
In reply to this post by Brad McEvoy-2
One of the supposed advantages of WebDAV is that it would work without
any software installed on the client.

However, when having to support lots of different versions of Office, OpenOffice
and  Windows, I'm wondering if it isn't actually better to install a
client that
works across all versions of Windows and have that be the interface
between Office and WebDAV.

I found some that are supposedly freeware. I haven't tried them.

http://www.bitkinex.com/webdavclient/
http://www.enginsite.com/ssh-webdav-ftp-sftp-client.htm

--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Daniel Lichtenberger
Hi Daniel,

I just thought I should point out that since we've got Digest
authentication you should be able to use plain http. I checked it a
while ago on Vista and it looked ok. But thats assuming your
authentication model allows Digest (ie you have access to the password)

Cheers,
Brad

Daniel Lichtenberger wrote:

> FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7. Things
> to keep in mind:
> * Microsoft decided some years ago to disable basic authentication over
> HTTP since it's totally insecure
> * I think that I never got old http:// mapping for WebDAV working.
>
> So, for example, the following URL format should work with "Connect
> network drive":
> \\<my-pc-name>@SSL\my-webdav-share
>
> Note that "localhost" or the IP address don't seem to work in this case,
> however, you can specify a port number after @SSL, as in:
> \\my-pc@SSL:8443\...
>
> Cheers,
> Daniel
>
> hank williams wrote:
>    
>> I was looking at the compatibility list here:
>>
>> http://milton.ettrema.com/compat/index.html
>>
>> In looking at the list it seems as though there are a fair number of
>> problems. Windows 7 isn't listed at all, and there seem to be problems
>> with every version of windows listed. Are these milton problem, or
>> would you say that windows just doesnt support webdav successfully. I
>> guess I am wondering if the problems listed happen with other webdav
>> servers or just windows.
>>
>> On the mac front, I guess the question is the same. Are the mac's
>> problems issues with *any* webdav server or just milton based webdav
>> servers.
>>
>> Thanks,
>> Hank
>>
>> --
>> blog: whydoeseverythingsuck.com<http://whydoeseverythingsuck.com>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Milton-users mailing list
>> [hidden email]
>> http://lists.justthe.net/mailman/listinfo/milton-users
>>
>>      
> _______________________________________________
> Milton-users mailing list
> [hidden email]
> http://lists.justthe.net/mailman/listinfo/milton-users
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Daniel Lichtenberger
In reply to this post by Brad McEvoy-2

>
> I think Daniel was referring to using windows drive mapping to connect
> to a webdav server (ie from the command line) where my-pc-name is just
> the machine name running milton, usually the local machine for
> developers.
>
> This particular MS dav client (there are several!) requires a windows
> UNC style address with the syntax given below. And Daniel's right, you
> can't access a server on localhost or 127.0.0.1, for some reason, it
> has to be a machine name.

Right. To be honest it didn't occur to me until now that this won't work
with complete domain names.

>
> Note that in most clients you specify webdav mount point as a regular
> http address, (which includes the windows "Add Network Location"
> feature),

Does "Add Network Location" work for you with Windows 7? I stumbled upon
the connect method I described only because the http[s]://.. syntax
stopped working for me.

Daniel

> but Gnome's Nautilus is also a bit odd, you must use DAV:// instead of
> http://
>
> Cheers,
> Brad
>
> hank williams wrote:
>> Thanks Daniel.
>>
>> This is a little off topic from my core question about how stable
>> milton is, but your comments do bring up some questions. I am new to
>> webdav and am not quite clear on the format you are suggesting.
>>
>> When you say the proper format is: "\\<my-pc-name>@SSL\my-webdav-share"
>>
>> I really dont know what that means. If I have a webdav server at
>> "somedomain.com <http://somedomain.com>" are you saying you need to
>> type "\\<my-pc-name>@SSL\somedomain.com <http://somedomain.com>"?
>>
>> And if so are you saying you need to put the port number before the
>> domain like "\\<my-pc-name>@SSL:8443\somedomain.com
>> <http://somedomain.com>" as opposed to after the domain, which is the
>> usual standard?
>>
>> And finally, why would you specify "<my-pc-name>" at all. I am
>> presuming here that <my-pc-name> is the name of the client you are
>> currently on, which is a strange thing to need to specify for an http
>> based protocol. If I go to google I dont need to specify
>> "http://<my-pc-name>@google.com <http://google.com>" since the name
>> of the local machine is somewhat irrelevant.
>>
>> Thanks
>> Hank
>>
>> On Thu, May 20, 2010 at 3:59 AM, Daniel Lichtenberger
>> <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7.
>>     Things
>>     to keep in mind:
>>     * Microsoft decided some years ago to disable basic
>>     authentication over
>>     HTTP since it's totally insecure
>>     * I think that I never got old http:// mapping for WebDAV working.
>>
>>     So, for example, the following URL format should work with "Connect
>>     network drive":
>>     \\<my-pc-name>@SSL\my-webdav-share
>>
>>     Note that "localhost" or the IP address don't seem to work in
>>     this case,
>>     however, you can specify a port number after @SSL, as in:
>>     \\my-pc@SSL:8443\...
>>
>>     Cheers,
>>     Daniel
>>
>>     hank williams wrote:
>>     > I was looking at the compatibility list here:
>>     >
>>     > http://milton.ettrema.com/compat/index.html
>>     >
>>     > In looking at the list it seems as though there are a fair
>>     number of
>>     > problems. Windows 7 isn't listed at all, and there seem to be
>>     problems
>>     > with every version of windows listed. Are these milton problem, or
>>     > would you say that windows just doesnt support webdav
>>     successfully. I
>>     > guess I am wondering if the problems listed happen with other
>>     webdav
>>     > servers or just windows.
>>     >
>>     > On the mac front, I guess the question is the same. Are the mac's
>>     > problems issues with *any* webdav server or just milton based
>>     webdav
>>     > servers.
>>     >
>>     > Thanks,
>>     > Hank
>>     >
>>     > --
>>     > blog: whydoeseverythingsuck.com
>>     <http://whydoeseverythingsuck.com> <http://whydoeseverythingsuck.com>
>>     >
>>     ------------------------------------------------------------------------
>>     >
>>     > _______________________________________________
>>     > Milton-users mailing list
>>     > [hidden email]
>>     <mailto:[hidden email]>
>>     > http://lists.justthe.net/mailman/listinfo/milton-users
>>     >
>>
>>
>>
>>
>> --
>> blog: whydoeseverythingsuck.com <http://whydoeseverythingsuck.com>
>>
>>
>> _______________________________________________
>> Milton-users mailing list
>> [hidden email]
>> http://lists.justthe.net/mailman/listinfo/milton-users
>>  
>

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Øyvind Harboe
I havent used those ones, but http://www.netdrive.net/ works a treat.
Free for personal use

Probably the best time to use it is when you're in development. You can
hang windows if you use a native client and your server doesnt give an
expected response, but netdrive handles it gracefully.



Øyvind Harboe wrote:

> One of the supposed advantages of WebDAV is that it would work without
> any software installed on the client.
>
> However, when having to support lots of different versions of Office, OpenOffice
> and  Windows, I'm wondering if it isn't actually better to install a
> client that
> works across all versions of Windows and have that be the interface
> between Office and WebDAV.
>
> I found some that are supposedly freeware. I haven't tried them.
>
> http://www.bitkinex.com/webdavclient/
> http://www.enginsite.com/ssh-webdav-ftp-sftp-client.htm
>
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Daniel Lichtenberger
In reply to this post by Brad McEvoy-2
Hi Brad,

yes, I thought of implementing Digest but it didn't seem to be worth the
tradeoff (must store plain-text password or precomputed hash instead of
just a salted hashed password).

Cheers,
Daniel

Brad McEvoy wrote:

> Hi Daniel,
>
> I just thought I should point out that since we've got Digest
> authentication you should be able to use plain http. I checked it a
> while ago on Vista and it looked ok. But thats assuming your
> authentication model allows Digest (ie you have access to the password)
>
> Cheers,
> Brad
>
> Daniel Lichtenberger wrote:
>> FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7. Things
>> to keep in mind:
>> * Microsoft decided some years ago to disable basic authentication over
>> HTTP since it's totally insecure
>> * I think that I never got old http:// mapping for WebDAV working.
>>
>> So, for example, the following URL format should work with "Connect
>> network drive":
>> \\<my-pc-name>@SSL\my-webdav-share
>>
>> Note that "localhost" or the IP address don't seem to work in this case,
>> however, you can specify a port number after @SSL, as in:
>> \\my-pc@SSL:8443\...
>>
>> Cheers,
>> Daniel
>>
>> hank williams wrote:
>>  
>>> I was looking at the compatibility list here:
>>>
>>> http://milton.ettrema.com/compat/index.html
>>>
>>> In looking at the list it seems as though there are a fair number of
>>> problems. Windows 7 isn't listed at all, and there seem to be problems
>>> with every version of windows listed. Are these milton problem, or
>>> would you say that windows just doesnt support webdav successfully. I
>>> guess I am wondering if the problems listed happen with other webdav
>>> servers or just windows.
>>>
>>> On the mac front, I guess the question is the same. Are the mac's
>>> problems issues with *any* webdav server or just milton based webdav
>>> servers.
>>>
>>> Thanks,
>>> Hank
>>>
>>> --
>>> blog: whydoeseverythingsuck.com<http://whydoeseverythingsuck.com>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> _______________________________________________
>>> Milton-users mailing list
>>> [hidden email]
>>> http://lists.justthe.net/mailman/listinfo/milton-users
>>>
>>>      
>> _______________________________________________
>> Milton-users mailing list
>> [hidden email]
>> http://lists.justthe.net/mailman/listinfo/milton-users
>>    
>

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Øyvind Harboe
In reply to this post by Brad McEvoy-2
On Thu, May 20, 2010 at 12:27 PM, Brad McEvoy <[hidden email]> wrote:
> I havent used those ones, but http://www.netdrive.net/ works a treat. Free
> for personal use
>
> Probably the best time to use it is when you're in development. You can hang
> windows if you use a native client and your server doesnt give an expected
> response, but netdrive handles it gracefully.

Ugh.... We're thinking about using WebDAV over non-LAN connections so
if Windows can become unstable with erratic connections that's icky...




--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Øyvind Harboe
In reply to this post by Brad McEvoy-2
> milton-test is intended to be a minimal implementation, while
> milton-filesystem-test adds some bells and whistles such as FTP and the web
> console. Is there something you can suggest to make milton-test simpler?

"all" I want to do is to create,re-save & load from within OpenOffice and
Office.

Perhaps all that is needed for milton-test is to iron out kinks so it works
for that case out of the box?

I thought I would be able to  extract that from the milton-test, but it
fails in refreshLock():

http://lists.justthe.net/pipermail/milton-users/2010-May/000494.html

--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Daniel Lichtenberger
Yep, it works for me **now**. Windows 7 has the peculiarity of requiring
unauthenticated access to the OPTIONS method. Milton was patched fairly
recently to allow this, so you might have had a milton version prior to
that one. The current version allows you to configure whether or not to
allow un-authenticated OPTIONS.

I want to do a bit more research and find out if that only applies to
the mount point, or if its all resources under the mount point as well.
If its just the mount point then its not such a security issue, then we
can have a feature in milton which allows you to specify the expected
mount point so we can get client compatibility out of the box without
having a gaping security hole.



Daniel Lichtenberger wrote:

>    
>> I think Daniel was referring to using windows drive mapping to connect
>> to a webdav server (ie from the command line) where my-pc-name is just
>> the machine name running milton, usually the local machine for
>> developers.
>>
>> This particular MS dav client (there are several!) requires a windows
>> UNC style address with the syntax given below. And Daniel's right, you
>> can't access a server on localhost or 127.0.0.1, for some reason, it
>> has to be a machine name.
>>      
> Right. To be honest it didn't occur to me until now that this won't work
> with complete domain names.
>
>    
>> Note that in most clients you specify webdav mount point as a regular
>> http address, (which includes the windows "Add Network Location"
>> feature),
>>      
> Does "Add Network Location" work for you with Windows 7? I stumbled upon
> the connect method I described only because the http[s]://.. syntax
> stopped working for me.
>
> Daniel
>
>    
>> but Gnome's Nautilus is also a bit odd, you must use DAV:// instead of
>> http://
>>
>> Cheers,
>> Brad
>>
>> hank williams wrote:
>>      
>>> Thanks Daniel.
>>>
>>> This is a little off topic from my core question about how stable
>>> milton is, but your comments do bring up some questions. I am new to
>>> webdav and am not quite clear on the format you are suggesting.
>>>
>>> When you say the proper format is: "\\<my-pc-name>@SSL\my-webdav-share"
>>>
>>> I really dont know what that means. If I have a webdav server at
>>> "somedomain.com<http://somedomain.com>" are you saying you need to
>>> type "\\<my-pc-name>@SSL\somedomain.com<http://somedomain.com>"?
>>>
>>> And if so are you saying you need to put the port number before the
>>> domain like "\\<my-pc-name>@SSL:8443\somedomain.com
>>> <http://somedomain.com>" as opposed to after the domain, which is the
>>> usual standard?
>>>
>>> And finally, why would you specify "<my-pc-name>" at all. I am
>>> presuming here that<my-pc-name>  is the name of the client you are
>>> currently on, which is a strange thing to need to specify for an http
>>> based protocol. If I go to google I dont need to specify
>>> "http://<my-pc-name>@google.com<http://google.com>" since the name
>>> of the local machine is somewhat irrelevant.
>>>
>>> Thanks
>>> Hank
>>>
>>> On Thu, May 20, 2010 at 3:59 AM, Daniel Lichtenberger
>>> <[hidden email]
>>> <mailto:[hidden email]>>  wrote:
>>>
>>>      FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7.
>>>      Things
>>>      to keep in mind:
>>>      * Microsoft decided some years ago to disable basic
>>>      authentication over
>>>      HTTP since it's totally insecure
>>>      * I think that I never got old http:// mapping for WebDAV working.
>>>
>>>      So, for example, the following URL format should work with "Connect
>>>      network drive":
>>>      \\<my-pc-name>@SSL\my-webdav-share
>>>
>>>      Note that "localhost" or the IP address don't seem to work in
>>>      this case,
>>>      however, you can specify a port number after @SSL, as in:
>>>      \\my-pc@SSL:8443\...
>>>
>>>      Cheers,
>>>      Daniel
>>>
>>>      hank williams wrote:
>>>      >  I was looking at the compatibility list here:
>>>      >
>>>      >  http://milton.ettrema.com/compat/index.html
>>>      >
>>>      >  In looking at the list it seems as though there are a fair
>>>      number of
>>>      >  problems. Windows 7 isn't listed at all, and there seem to be
>>>      problems
>>>      >  with every version of windows listed. Are these milton problem, or
>>>      >  would you say that windows just doesnt support webdav
>>>      successfully. I
>>>      >  guess I am wondering if the problems listed happen with other
>>>      webdav
>>>      >  servers or just windows.
>>>      >
>>>      >  On the mac front, I guess the question is the same. Are the mac's
>>>      >  problems issues with *any* webdav server or just milton based
>>>      webdav
>>>      >  servers.
>>>      >
>>>      >  Thanks,
>>>      >  Hank
>>>      >
>>>      >  --
>>>      >  blog: whydoeseverythingsuck.com
>>>      <http://whydoeseverythingsuck.com>  <http://whydoeseverythingsuck.com>
>>>      >
>>>      ------------------------------------------------------------------------
>>>      >
>>>      >  _______________________________________________
>>>      >  Milton-users mailing list
>>>      >  [hidden email]
>>>      <mailto:[hidden email]>
>>>      >  http://lists.justthe.net/mailman/listinfo/milton-users
>>>      >
>>>
>>>
>>>
>>>
>>> --
>>> blog: whydoeseverythingsuck.com<http://whydoeseverythingsuck.com>
>>>
>>>
>>> _______________________________________________
>>> Milton-users mailing list
>>> [hidden email]
>>> http://lists.justthe.net/mailman/listinfo/milton-users
>>>
>>>        
>>      
> _______________________________________________
> Milton-users mailing list
> [hidden email]
> http://lists.justthe.net/mailman/listinfo/milton-users
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Daniel Lichtenberger
Yeah, that can be difficult, especially if you're doing authentication
via LDAP or something where you just cant see the password.

Daniel Lichtenberger wrote:

> Hi Brad,
>
> yes, I thought of implementing Digest but it didn't seem to be worth the
> tradeoff (must store plain-text password or precomputed hash instead of
> just a salted hashed password).
>
> Cheers,
> Daniel
>
> Brad McEvoy wrote:
>    
>> Hi Daniel,
>>
>> I just thought I should point out that since we've got Digest
>> authentication you should be able to use plain http. I checked it a
>> while ago on Vista and it looked ok. But thats assuming your
>> authentication model allows Digest (ie you have access to the password)
>>
>> Cheers,
>> Brad
>>
>> Daniel Lichtenberger wrote:
>>      
>>> FWIW, I'm using Milton 1.5.3 quite successfully with Windows 7. Things
>>> to keep in mind:
>>> * Microsoft decided some years ago to disable basic authentication over
>>> HTTP since it's totally insecure
>>> * I think that I never got old http:// mapping for WebDAV working.
>>>
>>> So, for example, the following URL format should work with "Connect
>>> network drive":
>>> \\<my-pc-name>@SSL\my-webdav-share
>>>
>>> Note that "localhost" or the IP address don't seem to work in this case,
>>> however, you can specify a port number after @SSL, as in:
>>> \\my-pc@SSL:8443\...
>>>
>>> Cheers,
>>> Daniel
>>>
>>> hank williams wrote:
>>>
>>>        
>>>> I was looking at the compatibility list here:
>>>>
>>>> http://milton.ettrema.com/compat/index.html
>>>>
>>>> In looking at the list it seems as though there are a fair number of
>>>> problems. Windows 7 isn't listed at all, and there seem to be problems
>>>> with every version of windows listed. Are these milton problem, or
>>>> would you say that windows just doesnt support webdav successfully. I
>>>> guess I am wondering if the problems listed happen with other webdav
>>>> servers or just windows.
>>>>
>>>> On the mac front, I guess the question is the same. Are the mac's
>>>> problems issues with *any* webdav server or just milton based webdav
>>>> servers.
>>>>
>>>> Thanks,
>>>> Hank
>>>>
>>>> --
>>>> blog: whydoeseverythingsuck.com<http://whydoeseverythingsuck.com>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> _______________________________________________
>>>> Milton-users mailing list
>>>> [hidden email]
>>>> http://lists.justthe.net/mailman/listinfo/milton-users
>>>>
>>>>
>>>>          
>>> _______________________________________________
>>> Milton-users mailing list
>>> [hidden email]
>>> http://lists.justthe.net/mailman/listinfo/milton-users
>>>
>>>        
>>      
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Øyvind Harboe
Yeah, I think you're right. The demo app just needs some attention so it
can be used as a reference implementation. It tends to get a bit
forgotten about

Øyvind Harboe wrote:

>> milton-test is intended to be a minimal implementation, while
>> milton-filesystem-test adds some bells and whistles such as FTP and the web
>> console. Is there something you can suggest to make milton-test simpler?
>>      
> "all" I want to do is to create,re-save&  load from within OpenOffice and
> Office.
>
> Perhaps all that is needed for milton-test is to iron out kinks so it works
> for that case out of the box?
>
> I thought I would be able to  extract that from the milton-test, but it
> fails in refreshLock():
>
> http://lists.justthe.net/pipermail/milton-users/2010-May/000494.html
>
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Øyvind Harboe
On Thu, May 20, 2010 at 12:37 PM, Brad McEvoy <[hidden email]> wrote:
> Yeah, I think you're right. The demo app just needs some attention so it can
> be used as a reference implementation. It tends to get a bit forgotten about

I'm wondering if the refreshLock() implementation is broken in milton-test?

When I open, change & save a document in Office, createNew() is invoked
the second time so there are now two TBinaryResource() objects in
memory for the same file and only one of the has the TBinaryResource.
TResource.lock != null....



--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Øyvind Harboe
I don't think its an issue for network connectivity issues. I use built
in windows clients over the net daily and have never seen windows hang
due to network connectivity problems.

But i have seen some problems on Vista when i completely bollocks up the
response and send some garbage back.

Øyvind Harboe wrote:

> On Thu, May 20, 2010 at 12:27 PM, Brad McEvoy<[hidden email]>  wrote:
>    
>> I havent used those ones, but http://www.netdrive.net/ works a treat. Free
>> for personal use
>>
>> Probably the best time to use it is when you're in development. You can hang
>> windows if you use a native client and your server doesnt give an expected
>> response, but netdrive handles it gracefully.
>>      
> Ugh.... We're thinking about using WebDAV over non-LAN connections so
> if Windows can become unstable with erratic connections that's icky...
>
>
>
>
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Brad McEvoy-2
In reply to this post by Øyvind Harboe
createNew is expected to delete the previous resource, if one existed

Thats what checkAndRemove and TResource is meant to take care of. I'll
have a quick look at it...

Øyvind Harboe wrote:

> On Thu, May 20, 2010 at 12:37 PM, Brad McEvoy<[hidden email]>  wrote:
>    
>> Yeah, I think you're right. The demo app just needs some attention so it can
>> be used as a reference implementation. It tends to get a bit forgotten about
>>      
> I'm wondering if the refreshLock() implementation is broken in milton-test?
>
> When I open, change&  save a document in Office, createNew() is invoked
> the second time so there are now two TBinaryResource() objects in
> memory for the same file and only one of the has the TBinaryResource.
> TResource.lock != null....
>
>
>
>    

_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
Reply | Threaded
Open this post in threaded view
|

Re: state of milton bug status and stability.\

Øyvind Harboe
On Thu, May 20, 2010 at 12:45 PM, Brad McEvoy <[hidden email]> wrote:
> createNew is expected to delete the previous resource, if one existed
>
> Thats what checkAndRemove and TResource is meant to take care of. I'll have
> a quick look at it...

The old TResoruce is removed, but TResource.lock!=null in the old TResource....

Was the lock supposed to be "dropped"?


refreshLock() finds TResource.lock == null afterwards.

--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Milton-users mailing list
[hidden email]
http://lists.justthe.net/mailman/listinfo/milton-users
12