Mejedi,
Yeah, I would rather avoid reading the source. :( But thanks for the
pointers to the relevant source files. It would have taken me eons to
find those! I'll use code forensics to determine the actual protocol
where needed and will capture the findings in the protocol wiki page.
- Steve
--------------
Steve G. Bjorg
http://mindtouch.com
http://twitter.com/bjorg
On Dec 2, 2008, at 2:17 PM, ZNV wrote:
I believe you should read the source code to clarify the questions.
In particular,
kernel/gov/listener.cpp - client_listener() - swallows the first
message (CREATE_NEW_SESSION/se_Start-Up/110), starts new transaction
process that is responsible for the latter negotiation.
kernel/tr/tr.cpp - main() - the protocol in its full glory :)
kernel/tr/client_core.h,
kernel/tr/socket_client.h,
kernel/tr/socket_client.cpp - an abstraction layer between the
protocol logic and underlying socket connection.
WBR, Mejedi, former Sedna Team
2008/12/2 Steve Bjorg <[EMAIL PROTECTED]>
I should point out that the new .NET adapter is written in C# 2.0
and will be made available under Apache License 2.0. For those
interested in trying things out rather sooner than later, you can
get the trunk code from:
https://svn.mindtouch.com/source/public/sedna/trunk/
However be forewarned, this code is not yet tested! That said, the
more early feedback, the better! :)
On the diagrams, it would really help is the clarification questions
could be filled in. I can test the code for many cases, but some
require the server to send failure messages, which cannot be
forced. For example, what happens after the server sends the
BeginTransactionFailed message? Is the connection forcefully closed
or does it stay open?
The wiki page can be though of an "annotated client/server protocol"
document. This should be useful for updating the master document
from which it is pulled as well.
Cheers,
- Steve
--------------
Steve G. Bjorg
http://mindtouch.com
http://twitter.com/bjorg
On Dec 2, 2008, at 2:57 AM, Ivan Shcheklein wrote:
Hi Steve,
Over the Thanksgiving weekend in the US, I've been rewriting the
existing .NET adapter. The code was quite old and just by reading
it,
I spotted some bugs and concerns.
It's great. Indeed, .NET adapter is very old and buggy. Obviously
there is a need to rewrite it.
Anyhow, I've been reading the Sedna
Client/Server protocol PDF and have some questions concerning
ambiguities in the message flow and the underlying protocol state
machine. But before I fire away at them, I was curious if anyone has
already compiled a list of clarifications concerning the existing
spec? If not, I'll start a wiki page on the subject. Thanks!
There was no page before the one you started (I mean http://wiki.developer.mindtouch.com/index.php?title=Community/Sedna_XML_Database_Client%2F%2FServer_Session_Protocol)
.
Ivan Shcheklein,
Sedna Team
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win
great prizes
Grand prize is a trip for two to an Open Source event anywhere in
the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
