Arnulf Wiedemann wrote:
Am Freitag, 10. Juni 2005 09:52 schrieb Kay Ramme - Sun Germany - Hamburg:
Stephan Bergmann wrote:
Arnulf Wiedemann wrote:
[...]
[snip]
You mean a "text-based front end" to the URP bridge, so you can talk URP
"by hand?" No, I am not aware anybody already did anything in that
direction. But go ahead if you like... :)
The protocol is already exchangeable, so it should be sufficient to just
reimplement according to your needs/wishes. You should then directly be
able to use it e.g. from the UrlResolver etc.
-Stephan
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To get such a protocol I have started to add code to the urp marshaling and
unmarshaling functions using a special "Magic" at the beginning of the
message.
I use the size and message number bytes filled with the text string "ffffffff"
as the magic number which should be compatible with the existing
implementation because I think that combination does not happen otherwise.
That means the size value is set to 0x66666666 and the message number to
0x66666666 then the size and messagenumber are encoded as 0x.... text strings
followed by the rest of the message as a text string. That magic can be
easily checked in the readBlock function of the urp_reader. Depending on that
I set an additional variable for the type of protocol, which is checked for
in doing the unmarshaling.
The first request using that message with text-based encoding is running.
In principle you can mix messages of the old and the text-based format.
There are still 2 problems however, where I would be happy to get some hints
how to solve them:
- I need a remote/client environment which is done in the existing
implementation by a call to urp_sendRequest which in turn sets up a
ClientJob. Otherwise the urp requests returns a "no uno environment"
exception. I would like to do that via a text-based request to the urp
socket, but I don't kow what I need for the environment. Is there a
description of that available?
- the urp_writer write call is somehow modifying the start of my text-based
reply and I did not find the place where that is done.
What I would like to have after all is an urp interface without using ooo
librarys which would avoid all porting problems to different machines.
I would like to use such an interface to generate ooo documents(reports from a
database) from a scripting language and to convert them to - for example MS
Excel Format - for the user.
You should not call that protocol URP then. Even if you manage to
extend the existing binary UNO URP endpoint implementation to implement
your new protocol, other URP endpoint implementations (e.g., the Java
version) will not understand the new protocol.
Also, I am not sure whether your text-based protocol will be that much
simpler to implement in a given language than the current binary
protocol. For example, if you want to stay relatively close to URP in
your new protocol (which I assume you want to do, as you want to reuse
the existing binary UNO URP endpoint implementation), you have to
implement URP's object lifecycle model; that is, you have to send and
receive release messages in addition to any "true" messages.
-Stephan
Cheers,
Arnulf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
