& XSLT I'd say the way you're proposing to do it is probably the most reliable 
way. OTOH both the XML and the email handler are server-side to begin 
with, so why does the XML itself need to be round-tripped to the web 
browser? IE it must be stored somewhere (say in a database) so can't you 
just send back a form that says "email transaction X information", so 
maybe you'd have a set of checkboxes on your web form that would just 
have the X values. Probably you want to display some of the info on the 
form, but it would seem best to just format that as HTML as part of 
generating the form. It makes your emailing function a bit more complex 
and less generic, but if it has to undo base64 anyway its already pretty 
specific to that problem set, so why not just have it do the database 
lookup?

Les Richardson wrote:

> 
>  Hi All,
> 
>  As part of an XML transaction process with our provincial education 
>  department, I want to be able to automatically email some of the xml 
>  transactions (both sent and received portions) back to the provincial 
>  student records department so that we can have them solve the student 
>  authentication problems of certain transactions (these are typically 
>  student enrollment problems). This information is selected via 
>  feedback from a web form. (ie. administrator/secretary selects certain 
>  failed ones to email).
> 
>  The problem: To keep things are simple as possible (and stateless), 
>  the email function should simply accept the transaction information 
>  (ie. xml sent, xml received) and email these to the student records 
>  department for resolution. (along with some other school information, 
>  etc.)
> 
>  Can I just base64 encode the complete transaction (called a 
>  StudentSchoolEnrollment element, and the response) and then pass it as 
>  the value of a form element?  Then decode in the email generation 
>  function and put it into the text of the email?
> 
>  This just seems ugly and perhaps a more elegant solution exists? I 
>  just want to keep things as simple as possible and don't really want 
>  to do file I/O or session management, etc.
> 
>  Any feedback most welcome,
> 
> 
>  Les Richardson
>  Open Admin for Schools
>  Saskatchewan, Canada
>  _______________________________________________
>  Perl-XML mailing list
>  Perl-XML@[...].com
>  To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs


_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs