Re: [PyWrapper-devel] MOBY

[Javier de la T. <ja...@gm...>]

Good news,


> Yesterday I must have done something and TAPIR refused to start,  
> maybe some strange character in one of the data source files, I  
> don't know. Today I rebuilt the data source and TAPIR starts and  
> works fine. This just to point out that if anything happens to some  
> configuration files it is very difficult to figure out what is  
> wrong, so it could be a good thing to provide more feedback when  
> you are unable to startup TAPIR, at least list the file that breaks  
> the startup process.

Thats true, there is always the debug, but I know it can be hard...  
maybe the start script should say in which part did it fail to load  
more clearly...

>
> Regarding MOBy I have been trying the existing service and all  
> seems to work well, fast also. Now, what about the MOBY features  
> that TAPIR doesn't still support, I mean the ability to send more  
> than one query at the time and the ability to accept collections as  
> a query parameter?
>
The multiple invocations option I think is discarded for this version  
of PyWrapper. I dont think is that complicate to implement but I dont  
think is necessary to work on this in this version.
The ability to accept collections as a query parameter, although not  
tested, I think is possible to use it the way it is now... I dont see  
the problem transforming the moby request with a collection into a  
TAPIR filter with multiple conditions... but as I said I dont have  
any service with collections to test.

> Also users need the ability to refer to a custom MOBY central  
> registry.
>

Yes... thats true... do you need it now or can we wait a bit for me  
to be more free?

I see an incredible boost in your TAPIR and PyWrapper knowledge on  
the last two weeks!

Javi.