Bill,
It looks to me that the API will do the job. However, the callback interface
could be a little more specific.
Currently it looks like this:
public interface Callback {
void update (int number_collected, int number_in_queue);
};
This interface can only be used to update a progress bar. I would add at
least one more method to signal to an implementation that a resource was not
found. Also, I would pass the url of the current resource as well, so an
application can display a more specific message.
Ideally, every status message that the Python parser produces should have a
corresponding callback method. This means you'll have to fire the callback
events from within the Python parser itself. That said, I don't know Python
let alone the specifics of the parser, so I don't know it that's possible.
You can also take a look at how JPluck handles callback events. It uses the
JavaBeans Listener pattern.
http://home.planet.nl/~fridael/jpluck/javadoc/distantcord/plucker/spider/Spi
derListener.html
The JavaDoc is based on JPluck beta 2, the binaries and source of which I'll
release sometime next week. You can browse the rest of the JavaDoc but it is
spotty in places.
Regards
-Laurens
----- Original Message -----
From: "Bill Janssen" <[EMAIL PROTECTED]>
To: "Laurens M. Fridael" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 01, 2002 4:25 AM
Subject: plucker distiller Java API
> Laurens,
>
> Since it sounds like you know what you're doing in Java, I wondered if
> you have any feedback on the API notes I posted yesterday? Do they
> sound reasonable for an application that wants to call the distiller
> to do some work?
>
> Bill
> _______________________________________________
> plucker-dev mailing list
> [EMAIL PROTECTED]
> http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
