Re: [interopathon] Re: [soapbuilders] SOAPVerse - the kernel of an idea for an interoperability test/de mo
- Hi, Court!
--- Court Demas <court@...> wrote:
> - so Map is centralized - there is only one?Yes. Several maps means several games.
> - Is a crawler something which itself moves from room to room? OrExactly, interface for client.
> is it an interface for the client to move between rooms?
> - You say "get list of crawlers, choose one, etc...". What if twoThat's absolutely fine. It's just like class and you create instance
> clients choose the same crawler?
of it. Just means that they use the same implementation. All
information should go back and forth, and there is nothing to keep on
server side for crawler as far as I can see.
> - when is it "over"? It seems there should be some goal or endingAs soon as you (as a user) wants to stop it. The goal is to draw the
> point... for example, that each room was visited by a particular
map (you can draw your personal map, how did you go) for the whole
game that will show what rooms are most visited (server
implementations are most interoperable) and what crawlers are most
successful (clients are most interoperable) and more important what
the promblems were.
> Maybe you could have some information in each room which getsKind of. I'm not sure about stat that will be collected yet, but
> collected, and
> once you've been to each room you can easily determine whether all
> have been visited (prime number in each room, add them all up, or
> something like that).
that's the idea. Thank you.
Best wishes, Paul.
>=== message truncated ===
> Paul Kulchenko wrote:
> > Hi, Glen!
> > I was excited about the speed of decisions and the level of
> > understanding yesterday and now I'm observing the number of
> > issues around it today and it makes me ...hm, kind of sick, so
> > talk ONLY about technological aspects and I would be the first to
> > implement it as soon as we agree on it (and maybe even befor :)).
> > --- Glen Daniels <gdaniels@...> wrote:
> > > This is a quick writeup of an idea that a bunch of folks had
> > > week while
> > > discussing interoperability demos and tests. It's a pretty
> > > system
> > > which we thought was a) fun, b) technically interesting, and c)
> > > quite a compelling demo. I'd like to know what people think of
> > > idea - is this too ambitious, is it something you'd be psyched
> > I hope it's not and I agree with goals.
> > > help design/implement, is it cool?
> > I think it is and here is my view on that.
> > Map (A x B rooms)
> > Every room is server implementation (server)
> > Several crawlers are available to go throuh map (client and
> > Procedure for participants:
> > GET list of crawlers from Map
> > choose one
> > START with this crawler ([x,y]) and get back information where
> > are (crawler will MOVE_IN into specified room)
> > you may GET_LIST of other crawlers in this room, WRITE_NOTE for
> > other crawlers, READ_NOTEs posted by others
> > now you may MOVE your crawler somewhere (direction) and crawler
> > will tell current room MOVE_OUT and new room MOVE_IN. MOVE_OUT
> > shouldn't fail (otherwise you're locked in :)), because you
> > succesfully moved in, but MOVE_IN may fail, so you'll be in the
> > room.
> > Why do we need crawlers and do not tell directly where we want to
> > (MOVE_OUT to one room/server and MOVE_IN to another one)? First,
> > we really want to test interop both sides should be under some
> > control (not political :)) to log in errors and be sure that both
> > sides are doing it right. Second, it will let us to test
> > interoperability on two levels: from user to crawler and between
> > crawlers and servers. It'll let user switch crawler and keep
> > so after some time we will have map how crawlers are moving (and
> > where) and problem spots on our map. Providing different
> > to crawler (it could be web, GUI or something else) you can drive
> > thru the map, so it becomes accessible to (almost) everybody. Yet
> > you're able to call servers directly, but that's your
> > to handle and deal with errors, interfaces, etc.
> > Map interface
> > add_field(endpoint, details) -- register server to participate
> > add_crawler(endpoint, details) -- register crawler
> > get_list_of_crawlers
> > draw_the_map -- :)
> > Room interface
> > move_in
> > move_out
> > write_note
> > read_notes
> > get_list_of_crawlers_here
> > Crawler interface
> > start([x,y])
> > move(direction) -- does move_out from one and move_in into
> > one
> > write_note -- "I was here"
> > read_notes
> > get_list_of_crawlers_in_this_room
> > get_room_information
> > In my understanding central point IS required, just because both
> > server and crawler implementation should be REALLY simple and
> > NOT require any back-end, like persistent storage, databases,
> > not because it difficult or will take time, but just because
> > cut implementations that otherwise could participate, like Kafka
> > (XSLT) or I don't know, maybe SOAP.py. In my understanding (since
> > have both client and server in crawler) crawler should try to go
> > inside the room (different implementation) and then report to
> > result (no one else will be able to do it, current room doesn't
> > about it and new room may not know about it, because message
> > parsed). That's another reason why I think it shouldn't be just
> > client to talk to server, but specific crawler that will have
> > bit logic inside. Another important piece is that all reauired
> > information going back and forth and is not stored somewhere
> > client's computer (or maybe yet central point for stat) and it'll
> > switch crawler and keep going farther.
> > So, the picture is:
> > [any client: client, could be browser, applet, application,
> > /----- game borders ----------------------------
> > |
> > | [crawler: implements both client and server]
> > |
> > | [room: server only]
> > |
> > | [map: central point, control the game, server only]
> > |
> > \----------------------------------------------
> > In this picture Map should be MOST interoperable implementation
> > this time, because anyhow crawler and any other client should be
> > to talk to it. Then everybody can write server (interface is
> > and see how it goes. More efforts required to write crawler, but
> > more interesting also, and could be done independently. Anyway,
> > be able to check interop between users and crawlers and register
> > (hopefully) all issues and problems in interoperability between
> > crawlers and rooms.
> > Having central point will slightly modify the interface, so let
> > know if you think it IS or ISN'T required. Any thoughs will be
> > greatly appreciated.
> > Best wishes, Paul.
> > >
> > > The SOAPVerse : A long-term SOAP interoperability demo
> > > ------------------------------------------------------
> > >
> > > [1.0 Introduction - the view from outside]
> > >
> > > I'll start explaining the idea by giving a brief scenario. You
> > > connect a
> > > browser to SOAPVerse.org, which gives you three choices - 1)
> > > the
> > > SOAPVerse, 2) look at the map, and 3) learn about joining. You
> > > choose #1,
> > > and are offered a list of available clients and "entry portals"
> > > (i.e.
> > > clients (no, not "IE clients", necessarily...)) on the web.
> > > choose a
> > > local entry portal, and a Java applet appears, primarily
> > > of a text
> > > window:
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.