[Mono-list] A Plugin and WebService Issue

Pablo Fischer pablo@pablo.com.mx
Wed, 19 May 2004 20:14:36 -0500


--=-xQoOpxiXr0BFtZpmhseO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi!

I would like to have some comments and suggestions about a issue.

I am working in a Blog Client (mbloggy) that will work ONLY in SOAP (NO
XMLRPC) for different CMS and Blogs (phpnuke, postnuke, jaws, etc, etc).
To work with all these blogs I'm  planning to use a 'plugin' system,
based in assemblies, for example:

If a developer wants the plugin for a CMS (like drupal), he can save his
.dll plugin in ~./mbloggy/plugins and when mbloggy starts it will read
default plugins (in /etc/mbloggy) and the user plugins. When mbloggy
finds a new plugin it will be added to a 'drop down' (gtk#) so the user
can use it.

My problem?, yes, I don't know which is the best option:

a) Use .dll assemblies as plugins. But, how to connect to each plugin
from the front end?, exists a data type that can 'clone' another
object?, so I can do something like this:

Wrapper wrap =3D new Wrapper();
wrap.Clone("assemblie.dll");
wrap.Url =3D "http://www.foo.bar.com/foo.aspx?wsdl"
wrap.DeletePost(3);

So I can use the 'methods' of assemblie.dll in the wrap object?.

b) Or use just one .dll and let the developers to 'develop' just the
WebService (server)?, So I can just work like this:

Client c =3D new Client();
c.Url =3D "http://www.foo.bar.com/foo.aspx?wsdl"
c.DeletePost(3);

Which is the best option? and where can I find more information for the
best option?.

Thanks!
Pablo
--=20
Pablo Fischer Sandoval (pablo [arroba/at] pablo.com.mx)
Fingerprint:  5973 0F10 543F 54AE 1E41  EC81 0840 A10A 74A4 E5C0
http://www.pablo.com.mx=20
http://www.debianmexico.org

--=-xQoOpxiXr0BFtZpmhseO
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBArAZ8CEChCnSk5cARAk7MAJwPQLSnEgk0aebtheut4II+AdzZkQCdGTei
Fp73VGqBS7FItJJU/yAFT4s=
=s6Dc
-----END PGP SIGNATURE-----

--=-xQoOpxiXr0BFtZpmhseO--