On Wed, Aug 16, 2000 at 07:40:26AM -0400, Mike A. Harris wrote:
> On Wed, 16 Aug 2000, John Summerfield wrote:
>
> If I wrote such a beast, it would be straight C, with an API to
> plugin various frontends to such as discussed above. That way it
> works everywhere. You install the frontend for your prefered
> environment. No reliance on perl/tcl/tk/python or whatever...
>
yup
> >Unless there'sa good reason to use http, don't. You could
> >always prepare a datastream for a post, then mail it as an
> >attachment. Something at the bugzilla end reads the mail and
> >files the attachment.
>
> Does bugzilla have an alternate interface than http? If I were
> writing a client side frontend, I wouldn't be writing a bug
> reporting backend to replace bugzilla. If bugzilla uses http
> only, then http it is. I don't see any problem. I like the mail
> idea too though.
>
Heres my theory. When I get a chance, I want to add an xml-rpc
interface to bugzilla. info on xml-rpc is at http://www.xml-rpc.org.
It's basically a prettified method of using CGI. But it's just
stupid and simple enough to actually be kind of useful. xml-rpc
bindings already exist for python, perl, php, vb, C, java, and a few
others. It is dead simple to program with.
Once that's there, writing a frontend should be trivial.
xml-rpc can use either http or https as it's transport mechanism,
so it is firewall friendly (or unfriendly, depending on where you stand...).
And there will be some xml-rpc support in the next release for
other stuff.
> >If RHI is using an sql database, it shouldn't be hard to prepare and submit an
> >sql statement.
>
eeeek!
> Keep in mind the security aspects of this too. Submitting email
> to the thing needs to be secure. People could submit cron jobs
> or /fat32/autoexec.bat as a bug report directly. How would the
> server side handle it? How would authentication be done via
> email? With HTTP you have to log in. With email you have a
> sink. A sink open to spam and a horde of other things. It is
> possible but would have to be done carefully...
>
Anyone who wants to write a server based email "reciever"
is more than encouraged. I _think_ there is already a project
underway to do this, part of mozilla I belive.
> >Or maybe it should go dressed up as xml; that seems to be in
> >fashion right now.
>
> Ugg. Perhaps... The phrase "XML" is sounding more and more like
> the word "millenium" to me every day... getting sick of it. ;o)
>
agreed. xml-rpc is pretty lightweight and simple though. And
for an app thats already web based, an obvious way to try it.
> >> Who all is interested out there in taking on a project to provide
> >> a front end to bugzilla? If there are enough people, perhaps
> >> I'll start a new opensource project on source forge. I guarantee
> >> it WONT be called "bug pal" or anything anal retentive like
> >> that.. ;o)
> >
> >bugger.
>
> Heheh. That word has different meanings in North America, and
> Britain. ;o)
>
> If the text interface is "bugreporter", I'll assure that the GTK
> version won't suffer from the common "gbugreporter" braindamaged
> naming convention. ;o) I'm more inventive than that. Something
> like "gtkbugreporter". Hahaha. Just kidding! ;o)
>
> "crashomatic"? ;o)
I seemed to have missed the begining of this thread, so I
take it "bug-buddy" is broken somehow that doesnt make it approriate?
I would just like to see a xml-rpc interface, so that we could
easily implement clients that can submit, but can also query, update,
and other useful bits.
Adrian
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
