Dear colleagues,
a limited number of Abstracts' Book of the NETTAB workshop
on "CORBA and XML: towards a bioinformatics integrated network
environment", held in Genoa on last May 17-18, is now available
for free distribution.
Information on the Workshop can be found at the following URL:
http:/
Greetings,
If you're not interested in remote access to bioinformatics databases and
apps - STOP READING NOW!
Recently, I've been evaluating the ease-of-use, performance and utility of
CORBA vs. SOAP servers and clients. Particularly because SOAP's tunnelling
through HTTP can "smuggle" RPC requ
On Fri, Jul 13, 2001 at 12:03:07PM +0100, Alan Robinson wrote:
>
> Server details:
>
> - SOAP Endpoint URL: http://corba.ebi.ac.uk:/soap/servlet/rpcrouter/
>
> - Service name: "urn:simplebiosequence-service"
>
> - WSDL: http://corba.ebi.ac.uk:/wsdl/SimpleBioSequence_Service.wsdl
>
> -
On Fri, 13 Jul 2001, Thomas Down wrote:
> For anyone who wants to see what's going on behind the scenes
> in a SOAP transaction (or is just too lazy to install a proper
> client library ;-), the following XML snippet is a valid request to this
> server:
Nope, I don't want to see what's going on
This is wonderful!
Will Alan, will you be at BOSC this year?? I'd like to discuss
this with you.
-Brian
---
Brian Gilman <[EMAIL PROTECTED]>
Sr. Software Engineer MIT/Whitehead Inst. Center for Genome Research
One Kendall Square, Bldg
On Fri, Jul 13, 2001 at 02:12:37PM +0100, Alan Robinson wrote:
>
> Btw, using GLUE, the alternative is to add 3 JAR files to your class path,
> compile the WSDL and add the following *TWO* lines of code to your Java
> app:
>
> ISimpleBioSequenceService bioSeqService=SimpleBioSequenceService.bi
On Fri, 13 Jul 2001, Thomas Down wrote:
> Yep. GLUE is pretty nice, so long as what you're doing fits
> into the RPC-over-SOAP framework, and your messages don't
> get too big.
Can you define "too big"? Does this refer to request, response, or both?
cheers,
alan.
--
===
Dear All,
We've finally got around to adding pretty full support for parsing HMMER
output in the BlastLikeSAXParser. Specifically, HmmerSearch and
HmmerPfam. It should just work out of the box - i.e. you throw HMMER
output at the BlastLikeSAXParser, and it should deal with it.
As a consequence
