I've been writing documentation for a little while now and LaTeX always seemed the best way to solve the problem. You can make nice pdf and print version. Yes it takes some time to get use to and most WYSIWYG people don't like it but it rocks in CVS.
The DICOM (Digital Imaging and Communication in Medicine) standard is one implementation of the P2P that needs to be looked at. the principle behind the communication according to the DICOM standard is that EVERY "Station" is both a client and a server. you have of course dedicated storage station such as PACS (Picture Archiving System) for obvious reasons [the Files are quite large]. This standard is used and developed by people all over the world).
You can find one open source implementation of the DICOM standard here (OFFIS) and other DICOM ressourses here
Any How, this is only one example and I'm sure people can find better one.
I've resently made the switch from NSI to DomainDiscover. And i'm Happie the say that DomainDiscover HAS an online form for some operation. (Changing Contacts and Name Server). The forms still have some flaws(Like no back to main menu button when you have complited a change,etc), but overall they work well and do the job. Getting technical support there is also a fearly easy and fast (About no waiting on the phone). The transfer from NSI to DomainD. is quite easy, you just send them a form and they do the work for you. The only problem I've seen is when you have less then 60 days old domain at NSI. Since NSI Service agreement says that you have to wait for 60days before changing domains registrat, DomainD. will not be able to complete the operation before the end of that delay. Yours, Pierre-Luc
From my point of view, scanning email does represent in some what more of a problem... but look at it from the "bright" side, you don't read the proxy log to see wich WEB site where visited by whom etc.
Where I work (an High School) I have to monitor "Students" web trafic to ensure that there is "no" porn site visited and other "not allowed" sites. The only thing is that I don't only get to read the student trafic but also the "Staff" trafic forcing me to learn TO MUCH about some people by the web sites they visit when they think nobody is looking...
A good solution I found to that (and a good argument to prevent the "scanning") is to plead to my superiors that knowing "so much" about my coworkers would affect moral and relationship and would be a bad thing for everyone. The solution I proposed is to gather each log in a DATABASE and Run a small "home made" search engine to verify suspission on one individual.
Hope you could understand my poor: 3:30am english.
Slashdot Mirror
I've been writing documentation for a little while now and LaTeX always seemed the best way to solve the problem. You can make nice pdf and print version. Yes it takes some time to get use to and most WYSIWYG people don't like it but it rocks in CVS.
The DICOM (Digital Imaging and Communication in Medicine) standard is one implementation of the P2P that needs to be looked at. the principle behind the communication according to the DICOM standard is that EVERY "Station" is both a client and a server. you have of course dedicated storage station such as PACS (Picture Archiving System) for obvious reasons [the Files are quite large]. This standard is used and developed by people all over the world). You can find one open source implementation of the DICOM standard here (OFFIS) and other DICOM ressourses here Any How, this is only one example and I'm sure people can find better one.
I've resently made the switch from NSI to DomainDiscover. And i'm Happie the say that DomainDiscover HAS an online form for some operation. (Changing Contacts and Name Server). The forms still have some flaws(Like no back to main menu button when you have complited a change,etc), but overall they work well and do the job. Getting technical support there is also a fearly easy and fast (About no waiting on the phone). The transfer from NSI to DomainD. is quite easy, you just send them a form and they do the work for you. The only problem I've seen is when you have less then 60 days old domain at NSI. Since NSI Service agreement says that you have to wait for 60days before changing domains registrat, DomainD. will not be able to complete the operation before the end of that delay. Yours, Pierre-Luc
From my point of view, scanning email does represent in some what more of a problem... but look at it from the "bright" side, you don't read the proxy log to see wich WEB site where visited by whom etc.
Where I work (an High School) I have to monitor "Students" web trafic to ensure that there is "no" porn site visited and other "not allowed" sites. The only thing is that I don't only get to read the student trafic but also the "Staff" trafic forcing me to learn TO MUCH about some people by the web sites they visit when they think nobody is looking...
A good solution I found to that (and a good argument to prevent the "scanning") is to plead to my superiors that knowing "so much" about my coworkers would affect moral and relationship and would be a bad thing for everyone. The solution I proposed is to gather each log in a DATABASE and Run a small "home made" search engine to verify suspission on one individual.
Hope you could understand my poor: 3:30am english.