[Mono-list] wishlist
Daniel Morgan
danmorg@sc.rr.com
Thu, 2 Jan 2003 07:22:28 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0009_01C2B22F.B4DB8E90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
You or someone could create the SQLXML Managed classes found at
Microsoft.Data.SqlXml.
You could use the System.Data.SqlClient provider in Mono as a starting point
for it. We have a working DataSet, XmlDataDocument, DataTable, and a
working System.Data.SqlClient data provider. The SqlClient provider in Mono
is a Managed provider and was built using the TDS protocol in 100% C#. It
was written by Tim Coleman. It is based on jTDS and FreeTDS. Ville Palo
has been working on the XML functionality in the DataSet and XmlDataDocument
classes.
-----Original Message-----
From: mono-list-admin@ximian.com [mailto:mono-list-admin@ximian.com]On
Behalf Of Rein Petersen
Sent: Monday, December 30, 2002 6:38 PM
To: mono-list@ximian.com
Subject: [Mono-list] wishlist
I've only dreamed of using *nix in my web farm application but I have a
few needs to to contend with before I could. For one, a data provider that
mimics SQLXML managed classes would be a huge advantage. Microsoft built
their SQLXML managed classes using TDS and I believe I know approximately
how they have done it. Secondly, I'd need the ability to write modules and
handlers (and register them in web.config's would be nice). Also, a couple
of shortcomings MS has would be nice to overcome: for example, impersonation
is great but it the impersonated user requires all the permissions to allow
the dynamic compilation of the code. This is a security risk and makes the
use of impersonation unfeasible in many ways. It would be nicer if a section
of code could be run in context of the logged (or specifed) user and the
rest of the code, including the compilation, runs as the normal ASPNET
system user. Or, maybe it would make more sense to specify which user
account context is used when complilation is performed...
Rein
------=_NextPart_000_0009_01C2B22F.B4DB8E90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D248455911-02012003><FONT face=3DArial color=3D#0000ff =
size=3D2>You or=20
someone could create the SQLXML Managed classes found at=20
Microsoft.Data.SqlXml. </FONT></SPAN></DIV>
<DIV><SPAN class=3D248455911-02012003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D248455911-02012003><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
could use the System.Data.SqlClient provider in Mono as a starting point =
for it.=20
We have a working DataSet, XmlDataDocument, DataTable, and a =
working=20
System.Data.SqlClient data provider. </FONT></SPAN><SPAN=20
class=3D248455911-02012003><FONT face=3DArial color=3D#0000ff =
size=3D2>The SqlClient=20
provider in Mono is a Managed provider and was built using the =
TDS=20
protocol in 100% C#. It was written by Tim Coleman. It is =
based on=20
jTDS and FreeTDS. Ville Palo has been working on the XML =
functionality in=20
the DataSet and XmlDataDocument classes.</FONT></SPAN></DIV>
<DIV><SPAN class=3D248455911-02012003></SPAN><SPAN=20
class=3D248455911-02012003></SPAN><SPAN class=3D248455911-02012003><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D248455911-02012003></SPAN><FONT face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> =
mono-list-admin@ximian.com=20
[mailto:mono-list-admin@ximian.com]<B>On Behalf Of </B>Rein=20
Petersen<BR><B>Sent:</B> Monday, December 30, 2002 6:38 PM<BR><B>To:</B> =
mono-list@ximian.com<BR><B>Subject:</B> [Mono-list]=20
wishlist<BR><BR></DIV></FONT>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2>I've only dreamed of using *nix in my =
web farm=20
application but I have a few needs to to contend with before I could. =
For one,=20
a data provider that mimics SQLXML managed classes would be a huge =
advantage.=20
Microsoft built their SQLXML managed classes using TDS and I believe I =
know=20
approximately how they have done it. Secondly, I'd need the ability to =
write=20
modules and handlers (and register them in web.config's would be =
nice). Also,=20
a couple of shortcomings MS has would be nice to overcome: for =
example,=20
impersonation is great but it the impersonated user requires all the=20
permissions to allow the dynamic compilation of the code. This is a =
security=20
risk and makes the use of impersonation unfeasible in many ways. It =
would be=20
nicer if a section of code could be run in context of the logged (or =
specifed)=20
user and the rest of the code, including the compilation, runs as the =
normal=20
ASPNET system user. Or, maybe it would make more sense to specify =
which user=20
account context is used when complilation is performed...</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>Rein</FONT></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0009_01C2B22F.B4DB8E90--