I used to use Rational about 3 years back. Has any progress been made on Rational diagrams being stored as XML? It would be nice if all the Rational files would be in XML, and then use some kind of SVG browser to look at the diagrams, and make small changes directly from a web browser.
I know that load from from env differs from another env. However, my question was if anybody is "using" Tomcat+Cocoon in production env. And if so what is their experience?
Oh we were testing few other solutions as well. It is not like we spent 5 mnths just on 1 solution. Plus we have that kind of buffer (in timeline), where we can spend time on testing for 5-10 mnths.
Obviously you haven't researched the history books about the financial crash of 1920s. In 1920s the paper money was used to rip the people off more than half of their wealth.
Well, all I am saying the medium of transaction should retain it's value, and should not depreciate.
If I earn X amount of dollar today, and I can purchase a Acura NSX, I should be able to purchase the NSX even after 10 years with he same amount of $X.
The problem with paper money is that it has no intrinsic value, in 10 years time I would be lucky if I can purchase a Kia.
The value of paper money is controlled by a few a econmists, and they can manipulate the value, to make someone richer and everyone else poorer. And we have seen this happening many a times in history.
The only way to keep your keep you financial data private, is to keep you in Gold in a safe deposit in a bank.
Moreover Gold has intrinsic value as compared to paper money that has no intrinsic value.
I think it is high time, we all move above the Applications/OS wars. Instead of creating plugins for each application to go back and forth from each application formats, we should concentrate on the "Content Creation". When I use an Office Productivity Suite, my objective is to "Create Content", rather than make sure it works with apps from all vendors. But the sad reality is that, we are still involved in Application War.
I would prefer, that all the Office Productivity Suites, start supporting standard Document Models (DTDs/XSD) for content creation and management. DTDs like DocBook, WebSite etc. should be in all suites. Also Strict-XHTML suppport should be provided.
Offcourse this would no one would be able to monopolize the market by using obscure file format. But atleast this way, the war will move to "Content Creation" areas. Vendors will hopefull try to compete to include support for additional Document Models.
OpenOffice has it's own DTD, and I bet MS will soon implement its own DTD. This is now the right way to do things. They should work on to defining a standard DTD. But we all that is not going to happen. A happy medium would be to provide XSLTs to go from one DTD to another.
Check out tldp.org. All the documents are created usi ng XML/SGML. The idea offcourse is to ultimately create structured content, that can be queried and linked in future.
In my Unix Operator days, I used to get these calls. Actually they turned out to be beneficial (to the OS world).... I got some of the users to upgrade to StartOffice/OpenOffice or even Linux.
Well I guess if there was lots of research done, to just design the application (eg. pharmaceutical/medical), than the ransome model will be useful for getting the money back.
But for applications where very little research was involved, I don't think anybody would go for the ransome license model.
still not good as good as opensource
on
Software For Ransom
·
· Score: 3, Informative
The code/design that is reviewed and critiqued from the start is always better than the code that is the critiqued after the implementation. Again with the Ransome model, the design will not be as good as the opensource design model.
http://docbook.sc-icc.org
Check out the LAMPADAS project @ http://www.lampadas.org/index.html
But DSPACE concept pretty cool. I have been trying to design something like that using Cocoon and PHP
What about WebDAV over https:// using LDAP auth
on
E-Mail Size Limits?
·
· Score: 1
I saw a few posts about concerns over using FTP for sharing files. I completely agree with those people. FTP is far too in-secure. I would rather use scp or sftp.
But we use a better solution. We have WebDAV server with https:// (secured http) and LDAP authentication. The user just copies the files to a WebDAV location, using WebFolders and send the URL in the email. I also developed a application to keep track of who is accessing files etc. All this using Apache - not a single cent to buy any file sharing application. For more info: http://www.webdav.org or http://www.tldp.org/HOWTO/Apache-WebDAV-LDAP-HOWTO/
BTW all 3 major OSes (Linux, MacOS X, Windows) now support WebDAV natively
This i4i thing looks pretty cool. I must say I like it (well atleast the demo looks promising).
People hate change. If they fid out that this all works within Word, they would be willing to atleast give it a try....
At one point in time I was very involved in OpenOffice.org. Now I have lost track of the developement. There were some talk to including DocBook DTD in the distribution. Does anyone, if any progress has been made on that?
Are there any good classes/school/online courses where the document writers can learn to develope DocBook based content.
I have been writting for Linux documentation project for a while now. And I learned by looking at other XML/SGML content created by other people or machines. Is that the best way? Convert your existing non XML document to XML and go through it? I found that very useful in the begining. Any comments?
Whenever I try to compile davfs it fails, I do:
#./configure --with-kernel=/usr/src/linux-2.4.7-10
# make
and I get the following error message:
Making all in davfs
make[2]: Entering directory `/home/saqib/davfs-0.2.4/davfs'
gcc -c -o inode.o -O3 -Wall -DMODULE -D__KERNEL__ -DLINUX -fomit-frame-pointer -I/usr/src/linux-2.4.7-10/include inode.c
inode.c:622: parse error before string constant
inode.c:622: warning: type defaults to `int' in declaration of `MODULE_LICENSE'
inode.c:622: warning: data definition has no type or storage class
make[2]: *** [inode.o] Error 1
make[2]: Leaving directory `/home/saqib/davfs-0.2.4/davfs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/saqib/davfs-0.2.4'
make: *** [all-recursive-am] Error 2
Any ideas on how to fix this?
I understand that there is davfs and gnome-vfs and cadaver etc, however I would like to see some native DAV support in linux based apps. There are some nice Linux based desktop applications, that can gain a wider acceptance by including native DAV support.
RSA SecureID might be good. but it doesnt integrate with all systems:(
try to look into LDAP + siteminder. That might be the answer to your problems.....
Slashdot Mirror
I used to use Rational about 3 years back. Has any progress been made on Rational diagrams being stored as XML? It would be nice if all the Rational files would be in XML, and then use some kind of SVG browser to look at the diagrams, and make small changes directly from a web browser.
but very expensive. I hope IBM sells the licenses for cheaper.
I know that load from from env differs from another env. However, my question was if anybody is "using" Tomcat+Cocoon in production env. And if so what is their experience?
Oh we were testing few other solutions as well. It is not like we spent 5 mnths just on 1 solution. Plus we have that kind of buffer (in timeline), where we can spend time on testing for 5-10 mnths.
Obviously you haven't researched the history books about the financial crash of 1920s. In 1920s the paper money was used to rip the people off more than half of their wealth.
Well, all I am saying the medium of transaction should retain it's value, and should not depreciate.
If I earn X amount of dollar today, and I can purchase a Acura NSX, I should be able to purchase the NSX even after 10 years with he same amount of $X.
The problem with paper money is that it has no intrinsic value, in 10 years time I would be lucky if I can purchase a Kia.
The value of paper money is controlled by a few a econmists, and they can manipulate the value, to make someone richer and everyone else poorer. And we have seen this happening many a times in history.
The only way to keep your keep you financial data private, is to keep you in Gold in a safe deposit in a bank. Moreover Gold has intrinsic value as compared to paper money that has no intrinsic value.
I think it is high time, we all move above the Applications/OS wars. Instead of creating plugins for each application to go back and forth from each application formats, we should concentrate on the "Content Creation". When I use an Office Productivity Suite, my objective is to "Create Content", rather than make sure it works with apps from all vendors. But the sad reality is that, we are still involved in Application War.
I would prefer, that all the Office Productivity Suites, start supporting standard Document Models (DTDs/XSD) for content creation and management. DTDs like DocBook, WebSite etc. should be in all suites. Also Strict-XHTML suppport should be provided.
Offcourse this would no one would be able to monopolize the market by using obscure file format. But atleast this way, the war will move to "Content Creation" areas. Vendors will hopefull try to compete to include support for additional Document Models.
OpenOffice has it's own DTD, and I bet MS will soon implement its own DTD. This is now the right way to do things. They should work on to defining a standard DTD. But we all that is not going to happen. A happy medium would be to provide XSLTs to go from one DTD to another.
Check out tldp.org. All the documents are created usi ng XML/SGML. The idea offcourse is to ultimately create structured content, that can be queried and linked in future.
Take a look at http://www.i4i.com 's Tagless Editor
Still a lot cheaper than $1/min, and much more useful
In my Unix Operator days, I used to get these calls. Actually they turned out to be beneficial (to the OS world).... I got some of the users to upgrade to StartOffice/OpenOffice or even Linux.
Well I guess if there was lots of research done, to just design the application (eg. pharmaceutical/medical), than the ransome model will be useful for getting the money back. But for applications where very little research was involved, I don't think anybody would go for the ransome license model.
The code/design that is reviewed and critiqued from the start is always better than the code that is the critiqued after the implementation. Again with the Ransome model, the design will not be as good as the opensource design model. http://docbook.sc-icc.org
Check out the LAMPADAS project @ http://www.lampadas.org/index.html But DSPACE concept pretty cool. I have been trying to design something like that using Cocoon and PHP
I saw a few posts about concerns over using FTP for sharing files. I completely agree with those people. FTP is far too in-secure. I would rather use scp or sftp. But we use a better solution. We have WebDAV server with https:// (secured http) and LDAP authentication. The user just copies the files to a WebDAV location, using WebFolders and send the URL in the email. I also developed a application to keep track of who is accessing files etc. All this using Apache - not a single cent to buy any file sharing application. For more info: http://www.webdav.org or http://www.tldp.org/HOWTO/Apache-WebDAV-LDAP-HOWTO /
BTW all 3 major OSes (Linux, MacOS X, Windows) now support WebDAV natively
This i4i thing looks pretty cool. I must say I like it (well atleast the demo looks promising). People hate change. If they fid out that this all works within Word, they would be willing to atleast give it a try....
Yup Xalan definitely chokes. I have been thinking of replacing it. On the other hand AxKit looks good too.
At one point in time I was very involved in OpenOffice.org. Now I have lost track of the developement. There were some talk to including DocBook DTD in the distribution. Does anyone, if any progress has been made on that?
Are there any good classes/school/online courses where the document writers can learn to develope DocBook based content. I have been writting for Linux documentation project for a while now. And I learned by looking at other XML/SGML content created by other people or machines. Is that the best way? Convert your existing non XML document to XML and go through it? I found that very useful in the begining. Any comments?
Whenever I try to compile davfs it fails, I do: # ./configure --with-kernel=/usr/src/linux-2.4.7-10
# make
and I get the following error message:
Making all in davfs
make[2]: Entering directory `/home/saqib/davfs-0.2.4/davfs'
gcc -c -o inode.o -O3 -Wall -DMODULE -D__KERNEL__ -DLINUX -fomit-frame-pointer -I/usr/src/linux-2.4.7-10/include inode.c
inode.c:622: parse error before string constant
inode.c:622: warning: type defaults to `int' in declaration of `MODULE_LICENSE'
inode.c:622: warning: data definition has no type or storage class
make[2]: *** [inode.o] Error 1
make[2]: Leaving directory `/home/saqib/davfs-0.2.4/davfs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/saqib/davfs-0.2.4'
make: *** [all-recursive-am] Error 2
Any ideas on how to fix this?
I understand that there is davfs and gnome-vfs and cadaver etc, however I would like to see some native DAV support in linux based apps. There are some nice Linux based desktop applications, that can gain a wider acceptance by including native DAV support.
hmmm, but I haven't see any option in OpenOffice suite to access documents stored on DAV. There is nothing in the document as well.
RSA SecureID might be good. but it doesnt integrate with all systems :(
try to look into LDAP + siteminder. That might be the answer to your problems.....
I have already tried the httpd-ldap. it doesn't work :(