> What I mean - the implementation of this step in any available > Web-Server (100 and more version) is not really possible. The session > key must be build by the Web-Server > and as long as I know they are not valid after a server restart (in > most cases).
Thomas... let the webserver (whatever it is) and the admins which will want to implement the "attachment replacement" deal with such issues :) I mean; as I see it, if you'll decide to implement it, ASSP will *only* have to save the attachment somewhere and replace it with a "link"; the job from ASSP should then stop there ... no database or whatever; all the remainder doesn't belong to ASSP and it should *not* deal with it Just to refrain what I wrote; ASSP should just use a couple of parameters, that is, a path where the attachments should be saved and an URI (prefix) to use to build the replacement link; the path may be expressed using whatever syntax the underlying OS supports, so it may be something like /mnt/foobar/somepath d:\some\path \\server\some\share and ASSP will just use such a path to store the file; then it will strip it, calculate an MD5 (salted ?) checksum of the file and use the URI parameter to build the replacement link; the URI parameter may have whatever desired form, that is, it may be (e.g.) http://some.web.server/path/$FILE ftp://some.ftp.server/path/$FILE \\some.server\share\$FILE or even something like http://some.web.server/path/getfile.php?fid=$FILE and then some more; in any case ASSP won't even care nor deal with the file retrieval, it should just replace $FILE with the generated MD5 checksum (and the file extension) then... the tasks of dealing with "security" or with obsolete files cleanup should NOT be something handled by ASSP; the admin should setup things... e.g. writing a webpage (as for the "php" above) asking for some kind of authentication or setting up a scheduled script to archive/clean old files and so on; also, the attachment replacement should be optional, so that if one wants it, he may enable the option otherwise it will be disabled and attachments won't be striped/saved Again, let's avoid trying to force ASSP to do something which doesn't "belong" to it; yet, a simple, straightforward approach like the above may be feasible - given it's worth, by the way :D - I don't have such a need but given it was brought "on the table" I thought that the "right" approach to such a thing would be the above, that is, keep things simple and let ASSP *only* deal with email and totally ignore all the other aspects... letting the admin deal with them :) ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
