Re: Connection to Postilion over PostBredge - q2 based solution

[Mladen Mrkic]

Hi,

Thanks to all for help and suggestions.

I have a feedback concerning PostPackager.
According to Postilion documentation and real work with Postilion server I
made the following changes in PostPackager
in order to make it functional with Postilion server (in our case version
4.2):

field 52 (PIN DATA): IFA_BINARY ---> IFB_BINARY
field 127 (RESERVED PRIVATE USE): IFA_LLLBINARY ---> IFA_LLLLLLBINARY

With this changes PostPackager looks OK for us.

Best regards,
Mladen




Alejandro Revilla wrote:

>>Obviously, this work can't be accomplished with only one qserver.
>>We need two qservers and some way (some kind of space) for coordination
>>between this two qservers.
>>
>>
>>
>You can run multiple qservers, that's not a problem.
>
>
>
>>Any suggestion/comment is welcome.
>>
>>
>>
>Sounds like a qserver->connector->qmux->channel could do. You can either
>use some filters or work on an specific ISORequestListener
>implementation.
>
>The Spaces sounds like a nice thing that you can use to coordinate
>your server's activities (logon/logoff, etc.).
>
>If you are to conduct dynamic key exchange, then you can use
>the (persistent) JDBMSpace to easily store your cryptograms.
>
>
>.
>
>
>

[Alejandro Revilla]

>
> field 52 (PIN DATA): IFA_BINARY ---> IFB_BINARY
> field 127 (RESERVED PRIVATE USE): IFA_LLLBINARY ---> IFA_LLLLLLBINARY
>

I'd added a pointer to your message in src/config/packager/postpack.xml
as a reminder. I understand there's people using postpack.xml as it is
now, so I'm not sure if we should replace the current configuration...